The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

[*SPAM*] Re: Using Multiple Conditions in Determinators




Hi John
Have done what you suggested and i couldnt get the Determinator
to run based on a FirM
Zone and the value of a global...As a last resort i thought i would try and
copy the key value exactly as per the message...ie   keys=434a441144F1 and
it worked ;-))....Looks like its case sensitive what i entered was
434A1144F1(comparing the global value) and it wouldnt run........
So i now can open  Homevision Main Menu when  chan up from my dvd remote is
received from zone4  and close the Homevision Menu when chan down is
received from zone 8 ...;-))
Thanks John
Frank




----- Original Message -----
From: "John B" <home-automation@xxxxxxx>
To: <ukha_xpl@xxxxxxx>
Sent: Wednesday, September 29, 2004 5:24 AM
Subject: Re: [ukha_xpl] Using Multiple Conditions in Determinators


> Hi Frank,
>
> > > One way around this is to store the details of the last
infra red
signal
> > that was received in a global variable.
> >
> > Had a quick look but not sure how to do this ???
>
> The example below should take the value from the "keys="
body parameter,
and place it into a global called IR_KEYPRESS...
>
> In the Edit Determinator dialog, click on the Actions tab, and click
Add
to add a new action.
> Enter a name for the action, and select "Set the value of a
global
variable" from the action type dropdown list.
>
> In the Global Name box, enter the name of the global where you want
the
key code to be stored, e.g. IR_KEYPRESS
> In the Value box, enter
> {XPL::KEYS}
>
> (I think this needs to be all in uppercase)
> Basically, you can use a number of special keywords, enclosed in curly
brackets.
> The XPL:: prefix allows you to do things with any of the body
parameters
in the message that caused this determinator to fire.
>
> So, as it is a remote.basic message that has caused the determinator
to
fire, we can extract the value from the keys parameter by using
{XPL::KEYS}.
>
> Hope that helps,
>
> Regards,
>
> John
>
>
>
>
> xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
http://www.xpl.myby.co.uk
> To Post a Message: ukha_xpl@xxxxxxx
> To Subscribe:  ukha_xpl-subscribe@xxxxxxx
> To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx
> Yahoo! Groups Links
>
>
>
>
>




xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.