Is there a way to make the remote go to a certain page when it comes on? It always goes to the device list. I want it to go to the main Home page. But I can't figure out how. Any ideas???

Thanks

No, but notice that that only happens when you change the batteries.

For a very good solution to this, download one of the PCF files (in the NG files section) by David Shaw (aka Archer) and look at how he did it.

Barry

Nope no way to go directly to home.
Quick Synopsis:
1. Duplicate your home page in a new device and put that as the first device. Name the device start or begin. Personally I leave the name blank so no name is displayed on the button in step 2.
2. Remove all but one button on the Device Overview Template. (Advanced Mode) Make the device overview page look as you want with only one button. Make that button hold a bitmap saying anything you want.

For example my device overview screen has some graphics that say "welcome to my home theater" There is one button labeled Enter that when pushed brings you to the first device in your list. This device is a duplicate of my home page and is only used when the remote is first powered up or a new configuration is downloaded.

As bdorfman said Archer came up with this and we have just tweaked it to fit our styles.

I strongly disagree with this approach. The device overview page can be customized with your own buttons and putting the macro actions in the device properties action tab allows the device overview to function as your home page. Take a look at my .pcf to see how this is done.

Selecting the show device right and show device left buttons in the system page properties menu allows you to use these button to scroll in between devices w/o sending the IR codes associated with the device action macros. If you define a device as hidden it will not show up in the device overview nor will it be scrolled to using the device left/right buttons. It works pretty well and even my girlfriend can understand how to work the remote.

Working this way does not prevent you from constructing an action based interface, but it is much easier to program since many of the jumps and inteface programming you need to do is automatically generated for you. Play around with the interface and don't be tied to the model you are used to from the TSU 1000/2000. The new interface works pretty well.

--John
[email protected]

I will have to play with John's way to see if it is viable for me. John are you saying if you use the device overview page in the way it was designed that the remote remembers "state"? That is if I a choose to watch tv and then switch to DVD the remote will remember I was on TV and only switch as necessary to get me to DVD? I don't see how this could work in an action based remote. I will throw togehter a basic config and try it out.

Don

I don't think the device left/right buttons are a good solution for suppressing the device macros on large setups. If you have four or five devices, no big deal, but I have eleven, and it's not reasonable to expect guests (or even myself!) to remember what order they're in so as to avoid scrolling through page after page of devices. I had the device left/right buttons enabled when I first started programming my 3000, but I found I was never using them because it took too long to get to the device I wanted. Now I've disabled them and put "home" and "help" buttons where they used to be.

To me it doesn't seem unreasonable to want to configure the whole user interface, including the start page. I find it a little odd that the 3000 has a concept of a "home" device but doesn't appear to treat it any differently than other devices, apart from there being a built-in action to jump to it.

The way I have my remote set up I only use the device left/right buttons in an emergency, in other words almost never. I do however have a page which contains jumps to the TV, Amp and power devices (which are hidden) that allow me to get to these pages if I want to change the default operating modes (so I guess I'm cheating here as these are the moral equivalent of device right/left).

Don,

I'm not claiming that the remote remembers state (although state variables have been promised in a future firmware revision). However if you set up your device actions properly you should be able to get the remote to do the minimal amount of switching to go from mode to mode.

--John