All,

I have tried searching the forums but hard buttons have been the cause of so many threads that it's a little overwhelming...

Anyway, is there a way in PENG to set hard button commands at the page level? For example:
- "Jump to Channel Lists" from a main Tivo page.
- From the Channel List page, have the same button "Return to Main Tivo"

I know this is possible with any screen-based buttons but since the TSU3000 has so many more hard-buttons than the older Prontos, I'd like to take advantage of this if I can.

Thanks for any assistance.

-Mark

Not sure if I totally follow but the way I understand it:

If you duplicate that device, and on one hardbutton setting (device 1) you could program it to jump to the second (dupliate-device 2) device's Channel List, then on device 2 you could program the same button to jump to device 1 Main Tivo page.

Hope that helps

Your question is somewhat vague. There are 2 possible answers.

Based on what you state above, there's no problem in having Hard Buttons in devices jump to a page in the same or another device.

However, the thread subject implies a scenario like I describe below. In this case, Page-Level hard button definitions are not supported currently.

To accomplish page-level hard buttons, you have to separate pages that need the same set of hard buttons into their own device. For example, on my DVD player, I have 3 pages in a single device that have the 4-way cursor set up to do menuing. In a 2nd device with 'Transport' page, the 4-way cursor is set to control FF/REW/Play/Pause.

I have tabs setup in both devices that do the jumps to the appropriate page in the appropriate device.

For all the Philips remotes, things have to be done this way at the moment.

Lyndel

Thank you Mark and Lyndel for your replies. It now seems obvious but creating an additional device will take care of the issue for me.

If I wasn't clear before, what I'm trying to do is have the four labelled hard buttons perform certain actions from my TiVo main page then perform different actions from the channel listing pages. So my (now obvious) solution is to have an additional device for the channel listings pages. Problem solved! Thanks again for the help.

-Mark