On Fri, 27 Feb 2009 14:27:52 +0100 Michael 'Mickey' Lauer <[email protected]> said:
> Unfortunately that's not the full story. As I have repeatedly stated, > "busyness" is not just about user input, but also about input from > external sources. yes - thus my saying "fso is the broker - collecting such info" - never said this is the ONLY source. but it is what should be used to know when touchscren and/or keyboard is idle. :) > Feel free to disable the idlenotifier plugin in frameworkd.conf, it's a > one liner. (Of course I will not remove the idlenotifier at all, since > it's all we have, if X is not running) if u dont have x - you dont have a functional system... be it x or any replacement (an fb based app) it will have the same ability as x does as it is the one and only controller of the screen and input - so it can do the same. > You will then have to worry about the display being still dark when e.g. > the PIN dialog opens, or a call arrives. Oh and please take care about > applications that do not want autosuspend to trigger. apps should deactivate x screensaver as part of a toolkit call when such actions happen. > I absolutely not insist on _where_ that functionality is present, > though I insist _that_ the functionality is present. If > X/launcher/window manager wants to cover all that, be my guest, I have less > work then. > > -- > :M: > > > _______________________________________________ > smartphones-standards mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] _______________________________________________ smartphones-standards mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
