Yes, I know... I was referring to the earlier question of whether QUIT should be in the app-menu on window-menu, and whether or not QUIT should totally kill the app or just close the current window - an issue when several browser windows are open with several tabs each and in different work spaces...
Michael Catanzaro <[email protected]> wrote: >On Tue, 2013-11-26 at 06:50 +0100, Rick Opper wrote: >> So, an app can be kept running without any windows open then? Like on a >> Mac where all windows are closed but not the app? In that case, the >> app-menu would have QUIT, the window-menu would have CLOSE and SAVE, but >> then which one would have OPEN and NEW? would NEW be split? -> NEW >> WINDOW in app-menu, NEW DOCUMENT in window-menu? >> >> just being the devil's advocate... I have often quit my browser when I >> wanted to just close the current window. I don't think that's an issue >> with QUIT. Quit should kill the app. the X button should close the >> window. Maybe the app should quit it's self if there are no windows >> left... >> >> If we're going to have apps running with no windows then we need a way >> for users to see what's running - as opposed to what's open. QUIT would >> need to be both in the app-menu AND the context menu for apps in the >> dash... or something like that... > >No, closing the last window of an app does not leave it running in the >background. _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
