Closed capn-damo closed 8 years ago
Why a global var if it is only used in one statement?
I am digging deeper into this. Tests show that a trio of applications is involved: bl-exit, openbox and xrandr (setting or not setting the primary monitor)
It will not be evident to find a solution that works in all cases, without dragging in other python libraries.
By global I mean in a prominent place at the beginning of the script, so it would be easy for someone to edit. Slightly O/T now, after your other work.
ATM we have
(_, _, width, _) = gtk.gdk.Screen(BlexitWindowMerlin).get_monitor_geometry(0)
This works if the Openbox placement policy is "Smart", but not if it is "UnderMouse"
To ensure the exit dialog appears on a specified monitor, and not under the mouse on another one, and with the correct width,
rc.xml
needs to haveThis seems a bit clumsy, and requires the user to edit 2 scripts. Slightly better I think is to have a global var at the top of
bl-exit
:A better solution might be to detect where the mouse is, set
monitor
that way, and do away with the openbox config. And would this need to determine if "Smart" or "UnderMouse" is being used?