On 01/30/2017 01:06 PM, Carsten Haitzler (The Rasterman) wrote: > On Mon, 30 Jan 2017 08:24:05 +1030 Simon Lees <sfl...@suse.de> said: > >> Morning Raster >> >> I think this is still useful, It shows when you have an application like >> libreoffice or firefox blocking the shutdown giving an indication that >> something is actually happening, animations etc don't show up until >> after the final application is shown. (Yes i'm too lazy to close most >> applications before logging out). > > does it show that that is a problem? all it does is show what is blocking you? > i think this can just be done another way. > > that sys thing was an actual window that was "borderless" which it shouldnt > really be. i actually never hit something blocking my shutdown/reboot/logout > so > i never see the problem... but i know from simulating it that you are pretty > much left to figure it out yourself and it takes a while to timeout. > > what probably should happen is: > > 1. have a very short timeout (< 5 seconds - maybe 2 or 3) which should > negate > any need for any status. reality is any app should respond within this time > unless it's being really bad (either it's hung, swapped out due to very low > memory and a lot of it has to be swapped in for it to shut down, or it's doing > a "are you sure you want to exit with unsaved changes" kind of refusal to > close) > > 2. any windows that have not been closed by timeout, the user should be > taken > to and shown. > > #1 is a very quick fix. #2 is more of a feature add. > > i just really don't want to bring back those dialogs. they are from long > before > we did any compositing and so showing a "dialog" was pretty much the extent of > things we could really do nicely. admittedly i'm mostly interesting in the > suspend/hibernate as i really see no point having a dialog there as fading to > black is the slick thing to do because when you suspend or hibernate... that > is > the ultimate state of the screen in 99.9% of cases. same on shutdown and > reboot > and even on logout i would EXPECT whatever you log out to (likely the login > manager) to then restore the screen by "fading in from black" as that is what > would happen generally on boot and it's the one state i think everyone can > agree on as an assumed previous state (also black/off/backlight off is > where you can reconfigure resolutions and other modes and not have visible > artefacts if done right). :) so the only issues would be if 1. > suspend/hibernate/reboot/shutdown/logout is not working (and likely a lower > system issue in all cases EXCEPT the "apps refusing to exit cleanly" case). > > so how to deal with apps refusing to exit? we can definitely do it better than > we did before. >
Currently there is a dialog that comes up after a few seconds which gives you the option to cancel the logout or ignore those apps and logout anyway, if you make no decision after 1 minute it will logout anyway, this is really good behavior. Normally I press the logout now button but occasionally I find myself going oh crap I meant to save that or I forgot I had that virtual machine running, i'm going to cancel the logout fix the issues then logout again. As long as that behavior is kept I don't mind, As for taking the user there, thats harder then you think. Given I normally have 5 firefox windows (across several virtual desktops), Libre office on another virtual desktop and hexchat on another, all that will block shutdown how do you take me to all of them? half will launch a popup on the current desktop anyway. An extra nice feature might be adding a list of programs that block shutdown to an ignore list. For example firefox will always ask about closing X tabs and Hexchat will always ask about leaving networks i'm still connected too and in both these cases I don't really care where as if thunderbird does that means I have a draft email I forgot to send and i'd generally like to cancel the shutdown to make sure its sent. >> On 01/02/2017 08:25 PM, Carsten Haitzler wrote: >>> raster pushed a commit to branch master. >>> >>> http://git.enlightenment.org/core/enlightenment.git/commit/?id=8b9fee916ec3dfe5f60c0c4eabe187f500ee5b96 >>> >>> commit 8b9fee916ec3dfe5f60c0c4eabe187f500ee5b96 >>> Author: Carsten Haitzler (Rasterman) <ras...@rasterman.com> >>> Date: Thu Dec 29 21:14:28 2016 +0900 >>> >>> e sys - remove system action dialogs as comp actually does this >>> >>> so we have some dialog saying we're suspending/shutting down etc. etc. >>> and this is really pointless as comp already does a screen-wide effect >>> like fading out etc. and these dialogs were added long before we had a >>> compositor. there isn't much point anymore so remove them and let comp >>> deal with it. >>> --- >> >> -- >> >> Simon Lees (Simotek) http://simotek.net >> >> Emergency Update Team keybase.io/simotek >> SUSE Linux Adelaide Australia, UTC+10:30 >> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B >> > > -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
