[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: xPL Hal in a loop
- Subject: RE: xPL Hal in a loop
- From: "Tony Tofts" <tony@xxxxxxxxxx>
- Date: Wed, 8 Sep 2004 05:47:12 +0100
> The above script should only fire when B2 is actually
> switched on - not in response to a confirmation message, and
> it shouldn't be up to the user to check the schema themselves.
Hi Guys,
I can't really agree here.
There are 3 types of event (status, trigger, command) and the particular
event called is controlled by this type.
Even though x10 is built-in, it should be treated no differently to any
other schema. If we start putting in exceptions for this, we'll set a
precedent to start hardcoding exceptions for other schemas? Which to me
seems to defeat the point of the scripting system.
If anything it seems to indicate that x10.confirm should be a status rather
than a trigger?
Thoughts?
Many thanks
Tony
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|