Why this? A way to have a shared store of "variables" or states that
any part of e or modules can store some simple things in and thus also
broadcast changes to state, listen to changes in state and react.
I am thinking of things like advertising:
"/power/ac" = [ true | false ]
"/power/battery/low" = [ true | false ]
"/power/battery/charging" = [ true | false ]
"/power/state" = [ "on" | "sleep" ]
"/screen" = [ "on" | "dim" | "blank" ]
"/screen/locked" = [ true | false ]
"/network/online" = [ true | false ]
"/network/location" = "name of network detected"
so some apps/clients mess with screensaver/blanking/dpms behind e's
back. work around this - every 10 sec poll and check (ugly) and if
things are nto set as they should be ... force them to be set that
way. may lead to fights over this but too many people complaining
about steam or other apps messing with this.
You know...If we actually enforced our code formatting rules before
commit, then I could be saving a lot of time by not having to make a
bunch of formatting commits just so code is readable :/
NB: No functional changes
Something has changed in x where now rotated displays if you have
multiple screens don't vcome up right - an alternate for now is to run
xrandr commandline if it exsts. Not stricly a fix - a workaround.
wl does not have fallback rendering, therefore we always fallback to
default. In x11 we fallback to x11 rendering the cursor.
This should logically now not result in the cursor canvas beeing
deleted.
Make this dialog resizable for reading longer text (window titles,
etc). Also, fix the layout silliness that was going on by aligning the
table entries properly.
This dialog looked like crap :( Let's fix that :)
they insist on Type=XSession or you end up with a blank screen. this
was never defined as the standard. wm's have been using
Type=Application for decades! it's still documented in many places as
the way to add a custom session too. this is a workaround these stupid
DM's insisting on this. There is no good reason to make these changes.
For some reason I have yet to divine we don't get an initial unmap
event due to the reparent of the energyxt dialog windows and the
"ignore that first unmap" flag does not get cleared because it doesn't
happen. later when the dialog is withdrawn {9unmapped) this is ignored
then when you close the dialog... thus keeping it around as far as e
is concerned.
so to fix this - add a small timeout to clean this flag after a
show/map.
@fix