Monitor changes to can-suspend-to-RAM/Disk/Hybrid while config GUI is open?
This is a total edge case, but I was wondering. PowerDevil::PowerManagement
exposes these signals:
void canSuspendChanged();
void canSuspendThenHibernateChanged();
void canHibernateChanged();
void canHybridSuspendChanged();
Configuration KCMs only provide drop-down options for the suspend modes that are available on the given system. At KCM start-up time. However, if the device's suspend capabilities change while the KCM is open, we do not adjust the options. This raises three questions to me:
- Do these capabilities ever change at runtime?
- Is there ever any risk of letting the user select something their system (now) doesn't support?
- If these don't really change, why do we have signals in the first place?
- If these do change, how to deal with that in the KCM GUI?
- Should KCMs adapt their options at runtime? Would it be more confusing to the user if we remove their selection while the KCM is just sitting there but the device capabilities change?
- Should we keep the same options while the capabilities are disappearing, but check and possibly reject the selection once the user tries to save?
Just needed to jot this down so I can take out the TODO comment from my patch. GitLab issues are a better place to discuss this. If you have opinions, or you think this is just a waste of time either way, let's hear it!