TSU7000
I've looked but can't find an answer to this issue.
I watch TV through Tivo and I can navigate the guide with my thumb only with the cursor buttons.
I can then go to the Tivo home screen and do the same thing. Very convenient.
Then, once I'm watching a show, I would like the cursor buttons to change to fast forward and backward. This would allow me to keep just using my thumb.
So I was hoping that by switching pages I could tie the page to a different hard button behavior.
Is this possible?

In order to have different hard buttons per page, you have to split your pages into multiple activities/devices as the Firm/Hard key definitions are available only at the Device/Activity level.

One thing you may lose by doing this is the ability to use the Page Up/Down buttons on the side of the remote as I can't recall if you can program these with different commands like you can on the Pro Remotes. What you end up having to do is to 'wire' your pages together using onscreen buttons that do Jumps to specific pages.

That worked great. I made two Tivo devices, one with the cursor keys operating the menu: up, down, left, right - for use in the Tivo home screen and one with the cursor keys doing fast forward, backward, pause, and play - for use when I'm actually watching a recorded show or a live show.
Thanks

I only just got an RU950 last week so am still learning. But this seems to me to be a major limitation. The hard keys 'know' which device you are in but not which page. So they cannot be used for anything that needs to behave differently depending on which page you are on. Take the OK button. It might send a code for 'OK', then jump: from a TV-Guide-Categories page it should jump to a TV-Guide page, whereas OK on that page should jump to a Watching-TV page. But the OK hard key cannot know which page to jump to unless these are in different 'devices'.
These three pages could all be combined into one, but it would have to have a lot of buttons that are specific to different situations, it seems to me. Perhaps it could use tabs to hide irrelevant buttons while making them available when needed, on demand. In effect, the user is performing the jumps.
Alternatively, every such page could be put in a different 'device' in the pcf file. Not a problem, just inconvenient.
Am I missing something? What do others do? Am I trying too hard to minimise button presses?