I am doing something that should be fairly straight forward... If flag X is set then page link to page Y, else page link to page Z. All buttons are in stand alone mode. I am certain that the flag is set, but it seems that I am always taken to page Z as if the flag was not set. However, if I remove page Z from the "else" statement, I AM taken to page Y. What gives? Is there an issue with page links in flags? Could it be cause I am just testing this in emulator (preview) mode, and not on an actual RK2?

Help!!

make sure you don't have a page link on the actual button press, only in the macro. TT will override what's in the macro with what is directly on the button.

Certainly no page links or "assign to page" on any of the buttons.

Another thing to be aware of is how and where your flags are set and cleared.

I do this all of the time when creating multizone control from one device. When one zone is shut down a standalone test is executed to see first if another zone is still on and then what device is currently active in that zone so that the page flips to the active device in the active zone or... start a "goodbye" sequence.

The pain is that everytime you set a device or input flag, you must first clear all other like flags. If you are not linking a button directly to a page as mentioned in the other posts then I would examine where and when your flags get set and make sure that you are not overlooking any variables or steps in the logic.

Which remote? What firmware version?

Yea... I've checked this a couple of times.... This is where RTI needs some type of "flag status" window in preview mode for ease of troubleshooting.... I am trying to do something similar to what you describe... It is basically a K2 that controls a clubhouse theatre, and a separate tuner for exterior (pool side) speakers. However... the client wants the theater to be password protected, so I am having to flag the status of the theater and the clubhouse to know what page to back up to.. This stuff is hard to explain. :) I'll be happy to shoot over the .rti if you think you have time to review it. I would greatly appreciate any help.

thanks,
Dave

I will be up for 20 more minutes... email in my profile. If your late I will reply in the AM.

I don't use K2s but I went through the file and flagged it. It still didn't work in the simulator. I never used remotes from the T2+ config price vs. performance...

Thanks for taking the time to look at it.... I don't know what the heck is wrong with that.. I may end up sending it to RTI for their input/debugging.

Dave

send it over to the mail in my profile and I will take a quick look tonight when I get home.

I'm actually sitting here programming right now, just taking a quick break to eat, so if you want another opinion, send it my way too, and I'll plug it in.
Sounds like it could be a bug in TTD.

Send them the one I sent back this morning. Its almost funny when you see it just hop over the flags.

Ok... First of all... thanks to all who took the time to look over my programming. I emailed RTI, and here is what I got:

"Regarding your K2, it’s not really a bug, but the emulator will not track flags on the monochromatic devices. The color emulator WILL. So not really a bug, but an added feature to the color devices."

Nice that it's not a bug, but an "added feature"... lol

I did load a file on to a T2+ and it worked on the device.. just not in emulator.

Dave

Atleast it worked!

What is the sense of having the emulator even open the monochrome devices if it can't emulate the programming. You can already see what the bitmaps look like, so you don't need if for that.
I admit to never having opened the emulator for the T2+ systems I've programmed, primarily because they are pretty basic most of the time, and probably stand alone, meaning not part of a large system file, and therefore, easy to download and test.
But with the RK2, it could easily be a part of a larger system, and emulation of the programming is a valuable tool. How would monochrome be the key to emulation?
My two cents!

Because the Monochrom is the T2+ software. If you get in there and look at it, it is the only link to how RTI used to program. To be honest the software for the T2+ has very little in common when you compare it to the modern remotes.