08-14-2006 04:06 AM
08-14-2006 08:07 AM
08-14-2006 11:06 AM
... with the added bonus that it always triggers, even if the value actually does not change. For example of the current value is zero and you feed a zero to a value(sgl) property, the event will still trigger. 🙂
@TonP wrote:
Value Signalling, just triggers the event case just like a normal user value change.
05-10-2007 08:20 PM
Is there a way to get a val signal to work just like a user clicking a button to get a value change event (boolean in my case). It just repeatedly keeps triggering the events even though the value is not changing. I'm sure this may be useful in some situations but I need the programmatic signaling to work only when the value changes.
gtb
05-10-2007 08:27 PM
05-10-2007 11:22 PM
@gtb1234 wrote:
Is there a way to get a val signal to work just like a user clicking a button to get a value change event (boolean in my case). It just repeatedly keeps triggering the events even though the value is not changing. I'm sure this may be useful in some situations but I need the programmatic signaling to work only when the value changes.
Place the property node inside one case of a case structure and execute the case only when the value changes (e.g. compare with shift register value from the previous iteration). The other case is empty and executed when the value did not change.
Simple enought? 🙂
05-12-2007 12:25 PM
Thanks for the suggestions.
gtb