Why do event structures trigger duplicate events for value changed, sometimes?

[FrenchPress]

In this simple VI, an event structure is used to trap a value change within a color array.

However, when you run the VI and change a color, it triggers the event structure twice.  The second time the structure executes under the value change event, an impossible state exists where the structure is executing as if oldVal<>newVal, but they are in fact, equal.

I have had to write around this many times.  Why?

[altenbach]

I agree this behavior is wrong. Looks like a bug that is unique to colorbox constants. It does not happen if you replace them with numerics.

[FrenchPress]

Yes - I haven't tested all types of controls, but I know that most controls do not behave the same.  This is probably a bug.  I'm just trying to get confirmation from a support engineer that it's not something else that I've missed...

[altenbach]

For completeness, I reported it also in the February bug thread, so it should get noticed: 🙂

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=3385#M3385

[Joe_H]

And just to add something else that it should not do. If you click on it, it should open the color picker pallete what it should not do is fire the event if you click off in space somewhere and not actually change the color (which it does) which means they are triggering off of some type of mouse event.  This could be an annoying bug.

[JLS]

Hello,

This has been filed under CAR ID: 42FC9DIQ.

Best Regards,

JLS

Standard Response:

"This was reported to R&D (42FC9DIQ CAR ID) for further investigation. Thanks for the feedback!"

[Tournifreak]

I just checked this in 2011 - it's still there! Surely this ought to have been fixed by now!!??

[JÞB]

---

@Tournifreak wrote:

I just checked this in 2011 - it's still there! Surely this ought to have been fixed by now!!??

---

Its not there in 2012!  Huzza!

[Roy_F]

Jeff is correct - CAR 382786 was fixed in 2012, but not included in the bug fix list.