THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Ignas Anikevicius (gns_ank) ---------- Just my two cents and lots of rambling. What about awesome getting the info about the screen layout from randr? At least xrandr can give me the EDID of the screen, which should be pretty unique (if I understand what EDID is for correctly) and then awesome would be able to make more clever decisions. Also, IMO, we should store AWESOME_CLIENT_SCREEN **and** AWESOME_CLIENT_TAGS, make awesome aware of dynamic tag creation and deletion during restarts (e.g. if I add/delete some tags, they remain deleted after the Awesome restart). Then we can use the properties to unambiguously tag the clients correctly. The downsides should disappear in this way: - If the screens move arround, then Awesome would be aware of that and it would adjust the AWESOME_CLIENT_SCREEN according the the screen layout. - If the screen is added/removed, then Awesome will know that it has happened (new/missing EDID from the list). - When the screen is removed, then Awesome can put the leftover clients according to the awful.rules or to the primary screen current tag (or even create a new tag there, so that it's up to the user to clean things up and remove the tag afterwards). Is there anything useful out of this brain dump? ---------- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1155#comment3701 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to [email protected].
