I picked up a MX-980 and I have been learning the CCP software. I think I get most of it, but I do have one question...

I understand how variables work in general. It is clear how to use them in macros within IF statements and setting them on/off. What I don't understand is there is a "Variable" field in the property window for each button. What is the purpose of this field in the property window and how does it differ from using variables in macros?

Thanks
Robert

It allows you to set the state of a variable. Normally, you would do this in the macro window. URC probably sees it as a shortcut. :)

How do you set the state of a variable from the variable dropdown list of a buttons property? Just curious.


Being able to assign a button to a variable allows someone to show or hide buttons that are stacked on each other as well as change the displayed text. Very handy for making a remote feel more dynamic.

Interesting... let me try to follow what you are saying with an example. Say I have a button called "Display" on one of my TV pages. For this button, in the property window I create a variable called "TV Display" and then select that in the drop down list.

My guess is URC is doing one of two things with that variable....

1. It only displays that button if the variable is set to true?

2. Pressing the button toggles the state of the variable?

Thoughts?

Robert

Robert, did you ever discover the answer to your question here? I've been searching for the very same understanding and found this thread, but without a firm answer. I too am using a few Variables at this point succesfully, but would like to know about using the "Variable" field in the property window for a button itself. What exactly is that used for?

the variable field lets you change the button graphic based on the variable you assign it to.

if you look at the button properties window, you will see that there is a normal and pressed state for both the text and the image itself.

when the variable is true, it displays the pressed state of the image and text.

Okay, I'm probably being dumb, but how is this different than using the Text command down in the actual Macro instructions area? For instance, I have an If/Else statement that uses a Variable for determining the Power Status of a device that provides status commands via RS-232 thru my MRX-2. The query for status is sent to the device, the device responds with a certain string if it is indeed turned On. Based on that response, I then use the Text field to display the words "Power Is On" in bright green letters on the button that is normally called "Power Status". I then have a Delay to display that for a good 6 seconds. Then it goes back to being called "Power Status" again. (it of course does the Power is Off in Red letters if the On string is not returned). In this specific use case, how would the button choice at the top of "Variable" really help me? Would it for instance change the Button permanently? that would be strange, but interesting. Actually, stop the presses, I just tried it and it looks like the "pressed" text is available to you, but only stays there as long as the button is pressed, which is like 2 seconds. I believe this could be useful, but how is that any better/more flexible than my use of the Text command in the macro and then the nice delay of 6 seconds to ensure the user has plenty of time to see the visual display of the button?

Thanks again!

Because if you get creative using transparent buttons, you can have a single button show many different states based on variables.

Ahhh, interesting. I'll have to think about that for a while. Thanks!

Oops. Posted in the wrong thread.