On Thu, Feb 26, 2009 at 06:18:17PM +0100, arne anka wrote: >> Let me take your video player: most video players are audio players, >> too and you won't need the display in audio mode. > that's why i wrote _video_ player.
How many video-only players do you have installed? >> Please be aware of the fact, that the enabled display sucks really >> *a lot of* power > > well, that's my decision -- if i want the display on, i want it. > please, stay with the topic -- all these things are irrelevant to my > question. Sorry if I don't want this to become personally; I just think it's not so nice to have the display enabled the whole time for all users by default. > the terms are: there are applications that need an active display. how to > ensure, it stays on? period. there are only three ways - either modification of the applications which need an all-time-enabled display, writte a wrapper script, which does this or create the list in the framework and check if such an application is running before dimming the display. >> Don't forget one can already change the way of the application >> start, so that display is not blanked. This could be done in a 5 >> lines python script by first requesting display resource, then >> starting the desired app (given via argv) and finally release the >> display after the desired app stopped. > > that means, that one has to create for each such app an (additional) > desktop file. Either that or you change the existing one, yes. Basically it's a question of how many such apps exists. I only know of 3 cases: routing apps, video apps and games using accelometers only. The accelometers are very openmoko specific anyway and should implement the display request IMHO. So there are only the mapping apps and the video apps. > and what happens with the display if some other app or a > task switches the display back to auto? no other application can switch the display back to auto, since it still is in auto mode. The script just says the auto mode, that the display is in use and should not be disabled ;) You can think of it like a stack where each application using the display drops a message and removes it after it exits. You can't remove the message of another app and the display will only be dimmed when the stack is empty (as far as I understood the framework).
signature.asc
Description: Digital signature
_______________________________________________ smartphones-standards mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
