Performance fix.  The loadOnStartup status was being determined after the user had requested the Preferences be opened.  This was taking five seconds on an i7 2.66 GHz with an SSD, during which the Preferences were not displayed.  This code was moved to an async block run when Flycut loads, which should be fine since only the Flycut preferences change that setting.
Performance fix.  The loadOnStartup status was being determined after the user had requested the Preferences be opened.  This was taking five seconds on an i7 2.66 GHz with an SSD, during which the Preferences were not displayed.  This code was moved to an async block run when Flycut loads, which should be fine since only the Flycut preferences change that setting.

TermiT/Flycut,MarkJerde/Flycut,TermiT/Flycut,MarkJerde/Flycut,fiddlerwoaroof/Flycut,MarkJerde/Flycut,unkhz/Flycut,MarkJerde/Flycut,TermiT/Flycut,fiddlerwoaroof/Flycut,TermiT/Flycut,TermiT/Flycut