On May 27, 2014, at 5:55 PM, J. Landman Gay wrote: > It used to be that a Mac app should never quit when its last window was > closed, except in the case of single-window utilites. The menubar remained > and the app kept running. > > Now that Mavericks quits apps for you when the last window closes…
Another reason for me to delay running Mavericks as long as I possibly can. Is this true for apps like Word and TextEdit, too??? If so, my motivation is further reinforced. What the hell is Apple thinking of, changing its longstanding GUI conventions??? > ... (whether you want it to or not) should a Mac LC app do the same? The > problem with a LC app that uses the splash screen approach is that all > visible windows may be closed but the main app is still running, and the OS > will never quit it. Should the app be doing that itself now? In my admittedly few (and amateur) standalones, all built with the splashstack model, when I quit the primary working stack, it quits the application. I have to script it, but my assumption has been that this is what users expect from a standalone. But my apps have all been utility apps, and I don't want the OS making assumptions for me. An app that creates documents of any kind, each of which is in its own window, should most definitely NOT close when you close the last document. That's crazy. My attachment to Apple is being eroded step by step. It used to be a user-friendly, intuitive system. -- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
