I noticed that "stateless" rules (i.e. with if-true or if-false) are immediately executed on importXMl while the "normal" ones aren't.
Any specific reason why?
From my side I use some stateless rules to "listen" to e.g. motion control events or key presses, which shouldn't be executed on start-up.
As "workaround" I currently added a rule to check for "and initialized" where "initialized" is a object that is only set to true after some seconds.
To simplify that, I would propose to add an additional flag "init" to Rules, where
-if "yes",will always execute on importXML
-if "no", will not execute on importXML
-and if not defined, the old behaviour will remain for compatibility
Does this make sense? - If so I can prepare a patch.
Regards,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jeff, all,
I noticed that "stateless" rules (i.e. with if-true or if-false) are immediately executed on importXMl while the "normal" ones aren't.
Any specific reason why?
From my side I use some stateless rules to "listen" to e.g. motion control events or key presses, which shouldn't be executed on start-up.
As "workaround" I currently added a rule to check for "and initialized" where "initialized" is a object that is only set to true after some seconds.
To simplify that, I would propose to add an additional flag "init" to Rules, where
-if "yes",will always execute on importXML
-if "no", will not execute on importXML
-and if not defined, the old behaviour will remain for compatibility
Does this make sense? - If so I can prepare a patch.
Regards,
Michael