Question about Event Structure Behaviour

[Will.D]

"Is the issue that as you scroll around sometimes the Old and New value are equal" - Yes.

That and the fact that 2 events can fire while only one value change occurs (at least according to the "new value" indicator).  Seems to me that the "Event #" should EXACTLY correspond with the number of "New Value" changes.  I think the problem lies in the fact that occasionally a second event can fire which changes only the "Old Val", so that it is now equal to the "New Val".

This would make sense if the "New Val" also changed, but occasionally it does not.

[Matt_W1]

Ok I understand the problem now, I think I found a worse (and probably related) problem. If you drag the scroll bar in your example the old value will always equal the new value but only one value change event fired (at least for me in 8.2). So it looks like the old value just doesn't work right for scrollbars.

[jpeters]

Ok I understand the problem now, I think I found a worse (and probably related) problem. If you drag the scroll bar in your example the old value will always equal the new value but only one value change event fired (at least for me in 8.2). So it looks like the old value just doesn't work right for scrollbars.

I just tried this and you are right, that isn't working like it should.  This was reported to R&D (#43FDQ4GQ) for further investigation.

Jeff Peters

LabVIEW R & D

Message Edited by jpeters on 11-16-2006 02:57 PM

[parthabe]

hi Will,

One more thing I found out... I added a Mouse Move event to Ur VI & just replicated the code that tracks the No of events, I mean I wired the Shift Register part alone with a +1 between the registers.

I put the break point in this event case & ran the VI.

Everytime I reinitialized all the FP controls to Zero & then ran the VI.

To my disbelief & astonishment, I found that sometimes it triggers 2 events, sometimes correctly only 1.

Can all others pls try to repeat the problem again from Ur side... ?!

Regards,

Partha.