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]

Re: xPLHal scripting matches


  • Subject: Re: xPLHal scripting matches
  • From: John B
  • Date: Wed, 10 Sep 2003 17:26:00 +0000

> I have been scripting a feature to add on screen displays to the xPL
> callerID example and I do this by intercepting the class.type of
osd.basic -
> which is ideal - although I have to wildcard match all source
addresses.
>
> This works however it (as expected) cause all further matching
> within the XML file for filters to be aborted - as a match has been
found.

AH yes, this has caught me out on more than one occasion.

> Is there a way I can effectively say 'continue matching' such that any
later
> scripts will still be run - for example I would be stopping any later
source
> address matching.

I don't think so - not at the moment.

> Related to this I was also wondering if the default handling of
> breaking the matching when something happens is intuitive - or whether
> ongoing matching should happen by default and a script broken by a
form of
> 'break'instruction.. either way works of course.

I'd prefer it to carry on processing, and maybe issue something like:
sys.terminate() or sys.break() if you want it to not process any more
scripts.

Tony - could this be done?

> Just want this bit to be right and then I'll post this as a 'how to'
> for all, it also demonstrates use of the scripted xAP bridge feature
in
> xPLHal.

Excellent stuff Kevin.

Regards,

John






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.