The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: Quick schema queries


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

Re: naming comfort inputs? global var?


  • Subject: Re: naming comfort inputs? global var?
  • From: "slashcomfort" <yahoo@xxxxxxxxxxxxxx>
  • Date: Mon, 13 Jun 2005 11:43:21 -0000

yes, its for showing what triggered on a display. Did try setting this
up as a global but found it limited (in terms, i found the xpl message
for the specific sensor being triggered, selected to make a global, you
only get 1 variable to choose from - if you choose sensor, the global
reprepresents the sensor being triggered (rather than that specfic one)
so i guess determinator would be the way to go

Ade


--- In ukha_xpl@xxxxxxx, "John B" <home-automation@j...>
wrote:
> > sorry, newbie question - when you get a xpl comfort event, it
> > mentions the input number, is it a global variable i need to
> > create to change it to a name rather than a number so its
> > more readable?
>
> There is no way within the xPL Comfort app to have more friendly input
> names rather than numbers at the moment.
>
> Personally, I do use globals in xPLHal so that inputs are recorded as
> more friendly names and not just numbers.
>
> Where exactly is it that you would rather see or use names instead of
> numbers? E.g. is it for displaying which zone has triggered on an
> on-screen display? Or when you're creating determinators/scripts?
>
> Thanks,
>
> 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

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.