On Sunday 10 of February 2013 14:33:12 Alex Fiestas wrote: > On Sunday 10 February 2013 13:33:48 Daniel Vrátil wrote: > > > -connect to: org.kde.Solid.PowerManagement.profileChanged > > > > That's the way to go! > > ProfileChanged is not going to tell us what action "suspend to laptop" is > linked to :/ > > The workaround of using the config is mostly to be able to work with > anything that has been released up to this day, since for doing it properly > we'll have to wait until 4.10.1 > > Maybe what we can do is disable this feature for < 4.10.1 and patch > powerdevil to tell us what we want to know before next point release is > done. > > What do you think?
We should not only depend on Powerdevil's configuration, but in general ignore lid-closed event whenever suspend is in progress. The tricky part might be how to make sure we detect that the laptop is being suspended before we handle lid-closed event. Is that possible? Dan > _______________________________________________ > Kde-hardware-devel mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-hardware-devel -- [email protected] | Associate Software Engineer / BaseOS / KDE, Qt GPG Key: 0xC59D614F6F4AE348 Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-hardware-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-hardware-devel
