Roadmap to 1.5
Backlog
Bug fixes
Code cleanup
Improvements
sync the blanking or DPMS values between xfpm and X11
if the user sets the blank time e.g. in another application or a terminal (“xset s 10”), xfpm's UI wouldn't reflect this change of settings at all, but the screen would still blank after 10 seconds. however, this is more the exception than the rule, checking this once at dialog startup should be fine.
xdg-screensaver (which is used by many media players to suspend the screensaver during fullscreen-playback) seems to be causing some faulty behavior there by resetting the value to the X-default of 600s.
“Handle display power management” option also disables DPMS.
option a) We change the wording of the label to something like “Enable display power management”
option b) We make it do what it says, i.e. just leave the DPMS values alone if 0
further improve coexistance with xscreensaver (DPMS on AC/battery) if possible
consider doing a fade-to-black, if X11's screensaver extension is used (instead of gnome-screensaver or xscreensaver)
better handle machines that have more than one battery (especially warnings and remaining time, tooltip info about battery)
some machines (most common with IBM/Lenovo thinkpads) can set the maximum level batteries will be charged to (e.g. 80%); xfpm should properly handle this with regard to notifications etc. see
bug #8561
New features
detect installed/running lockers and add “Preferred lockscreen:” combobox to the settings-dialog (deprecates the “stupid” xflock script)
add “xfce4-power-manager –lock-session” commandline-switch (and also add that to xflock4 as first command to try)
-
we should probably also add a timed-locking feature to xfpm, so it really controls all locking options
-
add scale in the panel plugin to handle keyboard brightness
show current watt usage (upower energy rate available in battery info)
-
enables the user to easily apply additional low-level powersaving stuff that is out of scope of power manager (e.g. CPU frequency/governors, SATA link power management which can be troublesome on some devices)
at the moment, this can be achieved via udev rules
could be a hidden option, or on an extra tab
see bug
#8965, maybe an alternative solution for
#11127 and others (already closed)
add hidden? option(s) to execute a custom command for lock/hibernation/suspend/shutdown (see
#9683)