[maemo-developers] Optimal battery life considerations in apps
From: Anderson Lizardo anderson.lizardo at openbossa.orgDate: Fri Jul 24 13:57:42 EEST 2009
- Previous message: Optimal battery life considerations in apps
- Next message: Optimal battery life considerations in apps
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jul 24, 2009 at 4:54 AM, Andrew Flegg<andrew at bleb.org> wrote: > On Fri, Jul 24, 2009 at 07:55, daniel wilms<daniel.wilms at nokia.com> wrote: >> >> there is an API to detect if the window is in the foreground or not (thx to Kimmo >> for pointing me to this) [1]. If this property is true, then the window is visible >> on the screen. You can use this parameter directly from your root window. And here >> [2] you find the method to get the value of the parameter. > > Yup, indeed. (PyMaemo doesn't expose the method, but you can get the property). Hmm, here I can see this method just fine (Scratchbox X86 target): SBOX> run-standalone.sh python2.5 -c "import hildon; print hildon.Window.get_is_topmost" 2>/dev/null <method 'get_is_topmost' of 'hildon.Window' objects> I'm using Maemo 5 Beta 2 and python-hildon 0.9.0-1maemo10. > However, what's the best way of detecting when you come *back* to the > foreground? I didn't get a property-change event (although this could > be due to a PyMaemo bug rather than a Hildon one). If you could get a property-change event for any other property, I doubt that's a PyMaemo specific bug, because there would be no special handling for this specific property. If no property change at all is triggering this event, than that would be a bug :) Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil
- Previous message: Optimal battery life considerations in apps
- Next message: Optimal battery life considerations in apps
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]