On February 26, 2008 at 14:49, Darnitol said...
(Obvious formalities out of the way first: MX-890 = MX-980,
I'm assuming.)
It's a little hard to follow your question since it's
not formatted the way the MX-980 editor expresses it,
but I'm pretty sure I have the answer. Probably the key
you're overlooking is that MX-980 explicity supports IF/ELSE,
but not just IF. You need to declare both the "IF"
case and the "ELSE" case. (You can sort of do an IF by
keeping one side of the expression blank, of course.)
So first, in the If Setting dialog box, set your
trigger event. So, let's say you set the IF Setting for
a macro step to give the variable "FAIL" a trigger value
of "False."
Obviously at this point, you program your macro steps
for what happens on "IF," where the case of "IF" is that
when the macro is run, "FAIL" is set to False. The second
part of the macro therefore occurs when "FAIL" is set
to True.
Some even external to this macro step sets the value of
"FAIL," and the IF/ELSE statement acts on the valie of
"FAIL" to produce either the "IF" case or, if the "IF"
case is not satisfied, it defaults to the "ELSE" case.
Does that help?
Best regards,
Dale
To make the remote as easy as possible for my wife, I set a number of watch activity buttons, 'Blu-Ray, 'Cable' etc.
I don't want her to first press this button then press this button, then ....
So, when she presses 'Cable' button, a power on macro turns on all the devices, sets HDMI-2 on the receiver, then jumps to the cable page. She shouldn't have to know to first press the 'On' button.
But, if the devices are already turned on, then they shouldn't have to be turned on again if she decides to take a look at another device then come back to cable.
Absolutely no different than if you've already started your automobile then walked backed in the house to get something, you don't need to restart your vehicle again.
My logic in short is something like this:
TEXT (cable)
If ( UI(Var( POWERED_UP, False )
UI Var( POWERED_UP, True )
... turn the devices on macro ...'
ELSE
ALIAS(Receiver/Page3/HDMI-2)
DELAY(1.0 Second)
JUMP(Cable/Page1)
However, regardless of the value of my POWERED_UP variable, the devices are always turned on. The program flow doesn't seem to honor the value of the variable.
This is especially irksome for my cable box which doesn't have a discrete power on/off IR code. The software in the cable box has a bug and if the cable box isn't used for awhile while I'm using another device, then I lose connectivity to cable (I have to turn the cable box off for a few minutes then turn it back on again) so I need to set a variable that turns the cable box off only if the variable CABLE_PWR on is set to true and vice versa. In other words, if I call the power on/power off macros, then I need to turn the cable box on or off based upon the CABLE_PWR value.
The other thing that confuses me is how does one know what the state of a variable is? In most programming languages, you declare a variable then set it to a known value. In the MX-980 there is no entry code; no place to set your variable values.
It would be really nice it there was a debugger in the editor.
