Jack or AHP,

Thanks very much for your responses in my previous posts. I do have one further question relating to how long the screen/lights stay active after you last touch the screen.

I have found that depending on my use, I would like this delay to be programmable. I know that you can set some global defaults in the SETUP menu, but here is an example of what I mean.

When I'm on the TV page, the screen can turn off within about 5-10 seconds because I rarely need to issue multiple commands separated by more than that delay. However, for my VCR device, I would want the delay to be much longer because its a real pain when you are fast-forwarding through commercials and the screen goes off because by the time the screen turns back on you have gone too far. So for the VCR device, I would want the timeout to be 30-40 sec.

I know that by setting a longer delay, I'm using much more battery power so is there another way
to do this with the software? If not, is this a feature that can be added in future releases of the software?

Sean

Just thought I would put my 2 cents in on this one. This is pretty much why the hard buttons are programmable and available without waking the unit at all. I basically did the same thing you are talking about for the same reason for my DVD already..

Because the hard buttons can be device dependant, you can set the left/right buttons to be RW and FF when you are at the VCR page and the Channel buttons be Stop/Play. I chose this because the left/right buttons are too easily pressed for start stop... but you want easy access to them in order to stop FF and continue playing.

If you set the vol & channel buttons as global in the start, then no other devices will be affected.. this functionality will only happen when you switch to the VCR from the home page or device list.

Hope that helps.

Sean,

Sorry, no variable at present in release that I have. I would guess it's a global that wouldn't be that easy to write around, although of course anything is possible as it is software. It would have to be "device" related else how would Pronto know what timeout you wanted.