On 02/24/2012 08:02 PM, Bill Spitzak wrote:
> Tiago Vignatti wrote:
>> DISPLAY_ON → DISPLAY_DIM → DISPLAY_SCREENSAVER → DISPLAY_OFF
>
> Won't there be some interest in making the backlight dim *after* the
> screensaver starts? I can imagine the control ui being a bunch of
> timing sliders, which t
On 02/24/2012 09:02 PM, Bill Spitzak wrote:
Tiago Vignatti wrote:
DISPLAY_ON → DISPLAY_DIM → DISPLAY_SCREENSAVER → DISPLAY_OFF
Won't there be some interest in making the backlight dim *after* the
screensaver starts?
hum, I don't see a real usage for such. I don't think we have to be that
fl
Tiago Vignatti wrote:
DISPLAY_ON → DISPLAY_DIM → DISPLAY_SCREENSAVER → DISPLAY_OFF
Won't there be some interest in making the backlight dim *after* the
screensaver starts? I can imagine the control ui being a bunch of timing
sliders, which the user can move anywhere. Thus the screen saver can
DISPLAY_ON → DISPLAY_DIM → DISPLAY_SCREENSAVER → DISPLAY_OFF
transitions between states happen in this same sequential way and it's based
on time of user idleness. Once some (input) activity is generated, then it
jumps back to the first state.
We're still using one single timer for this implement
