04-25-2006 09:27 AM
04-25-2006 09:58 AM
04-26-2006 04:08 PM
04-26-2006 06:47 PM
In addition it is worth pointing out that it triggers a value change event even in the value actually does not change. For example, If you send a FALSE to a signaling property of a boolean that is currently FALSE, the event still fires. Can be quite useful. 😄
@jls wrote:
Yes, the Value (Signaling) property will change the value of a control (or indicator) as well as generate a value change event for that control or indicator, which can be handled by an event structure.
04-27-2006 07:16 AM
In addition it is worth pointing out that it triggers a value change event even in the value actually does not change. For example, If you send a FALSE to a signaling property of a boolean that is currently FALSE, the event still fires.
Yeah, I found out that part the hard way. Oh well, no real harm done though.
George
04-27-2006 07:20 AM
It's all part of the fun of learning LV.
Yes.... those Global & Local Variables are very tempting....
.... and so was some sort of apple 6000 years ago 😉
07-13-2006 06:20 PM
07-13-2006 06:47 PM
@Tariah wrote:
I just spent a painful day trying to code a shared-variable event-handler and discovered the hard way what altenbach mentioned.A shared variable triggers a value change event even if the value actually does not change.
Don't put words in my mouth, I never said that! 😮 I wasn't even talking about shared variables. I was talking about writing to Signaling Value Properties of some other hidden control. (Even if the new value we write is derived from a shared variable in some way, a rather irrelevant fact in this context).
Shared variables don't trigger events!
07-13-2006 08:39 PM
07-13-2006 09:08 PM
@Tariah wrote:
And they do trigger the event without actually changing value. Pretty useless.