[maemo-developers] backgrounding/lock QA fail
From: Ian Stirling maemo at mauve.plus.comDate: Mon Aug 16 14:24:32 EEST 2010
- Previous message: backgrounding/lock QA fail
- Next message: Fwd: backgrounding/lock QA fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Attila Csipa wrote: > I see we have a few apps (especially ports and stuff using SDL) that do not > know how to suspend themselves and therefore it fails the QA. > Now, I was thinking, as this sort of > bug is a kind of a 'be aware' type, is that maybe we could allow these to pass > if they made it clear to the user they are not able to suspend themselves. A > popup after install, or a Hildon banner before/during startup... that sort of I would with some hesitation agree to this. For some apps, it's probably the only sensible route. Expecting the porter of a huge app that did little more than simply package it, and write 3 or 4 lines of description to take the leap to screwing with core portions of the event loop is hard. It should not be a blocker if there is no practical way to change it. But for apps where it should be possible to change this easily, it should remain. http://wiki.maemo.org/N900_Software_Power_management - I'm planning to populate with links to info on how to change, as well as flesh it out some more.
- Previous message: backgrounding/lock QA fail
- Next message: Fwd: backgrounding/lock QA fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]