On Thu, 28 May 2015 22:15:18 +0200 Massimo Maiurana <[email protected]> said:
> Marc MERLIN ha scritto il 28/05/2015 alle 22:00: > > > Actually, just to be clear: I have 3 virtual screens, and I just got the > > bug again. All my windows of all 3 virtual screens got centered in their > > respective virtual screen. > > Does this match the problem you're describing? > > > > Is there any workaround? This is starting to be problematic for me :-/ > > There is one in current git as Raster said. > I had a similar problem but in my case windows were changed in size > instead of being centered, always after a resume from suspend. > > In current git there is now two new options in screen setup dialog, > "monitor hotplug" and "lid events"; unchecking the latter did the trick > for me ;) yup - so i am listening to feedback on the new randr code and as people point out issues am fixing them (in some cases the only sane fix is either to totally drop a feature - eg auto reconfig of screens on plug/unplug or like the above - add an option if you happen to suffer from it, as drivers all behave differently - for example nvidia doesn't go indicate monitors are disconnected just because they are dpms turned off, but it would seem intel does (which imho is a bit broken on the part of intel)). a more involved way to address screen hotplug is to add some "purgatory" system. when a screen is unplugged, the screen and all its desktops and content are put into "purgatory". the screen and content exist, but only via some tool/ui (eg some popup from the pager on other screens?). you can see what is there in this tool, but otherwise not interact or see the apps. using this tool you could then choose to: 1. dump a screen onto another screen (merging windows) 2. pick a specific window to move to your current screen (like you can dnd in the pager already) 3. delete the screen and all its contents (don't need it anymore) 4. just leave it alone and do nothing you can go do the above any time at all. now we need to remember EXACTLY which monitor this screen was configured for (edid etc.), and keep that stored in the screen (zone in e terms). if that screen gets plugged back in, e automatically pulls this screen out of purgatory and puts it back where it was, but only in this case. but this of course is far far far more work and more involved, and is some major altering of e's internals to get things like "hidden zones" to work. also the ui to do the control etc. and i want to ensure the randr code we have is solid long before i launch into exotic ui changes like this. i'm doing "baby steps". one thing at a time and ensuring it is solid before doing the next. at least for all the cases i have seen and tested the new randr code is now very solid. if people find issues, please report. try e in git if you have "screen/randr issues" and tell me. i recently adapted the code to auto-pick a common resolution for cloning based on feedback from zmike. so try it, get me info if you have issues and we'll move forward over time. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
