strict type enum not firing event

[Been bitten by LabVIEW]

Has anyone seen this before?  Couldn't replicate it for a while until I tried to make a control a strict type.

This is a big problem since I use strict types to ensure that the types don't get out of sync if they are changes for whatever reason.

What happens is that I fire an event using property Val(Sgnl) and though it changes the value on the control, no event is fired.

I've attached a VI showing this.  Do the following:

1. Run test events.vi
2. Press Fire Events button
3. Note that Events Fired control shows only "Ok: TRUE -> TRUE"
4. Press STOP
5. Right click on control labeled Numeric.
6. Select "Disconnect from Type Def."
7. Run VI again
8. Press Fire Events button
9. Note the Numeric events are now fireing.
10. Press STOP
11. Right click on control labeled Enum.
12. Select "Disconnect from Type Def."
13. Run VI again
14. Press Fire Events button
15. Note the Enum events are now fireing.

Does anyone have a solution for this besides disconnecting the control from it's type def?

I'm using LV 7.0 on WinXP.

Thanks


Adrian

[NitinD]

Hi Adrian,

I can reproduce the behaviour you are describing in LV 7.0, but it has been solved in newer versions of LabVIEW. In LV 8.0 onwards, the results are same for steps 1-3, steps 5-8 and steps 11-14.

Hope this helps.

[Been bitten by LabVIEW]

So is there is no way of fixing this in LV 7.0?

[Been bitten by LabVIEW]

Oh, BTW, no it doesn't.  Unfortunatly, we are currently stuck using LV 7.0.  Legacy. 😞

[NitinD]

I will try and dig up the CAR database and see if there was a work around for this, but you'll have to give me some time... I'll be able to this in the next week probably... Meanwhile, I just hope someone else can help you. 🙂

[Ben]

A non-strict is unaceptable?

Ben

[Been bitten by LabVIEW]

On a semi-related note, when using the the user events, they appear to fire (be injected in the event queue) at random times, and not immidiately before or after the main event handler.  Why would that be?

Attached is sample code.  Run the VI and press Fire Events several times.  Then click on the Events Fired box, go to the begining (ctrl-home) and then press page-up/page-down to see that the Enum2 events are being handled some time after the Enum event.  Also, if you notice, they don't even appear in order that they were fired.  (I.e. Enum2 firing 2+ times before Ok2 being fired when they should be interlaced). WTF??

[Been bitten by LabVIEW]

---

Ben wrote:

A non-strict is unaceptable?

Adrian wrote:

This is a big problem since I use strict types to ensure that the types don't get out of sync if they are changes for whatever reason.

---

[Been bitten by LabVIEW]

---

NitinD wrote:
I will try and dig up the CAR database and see if there was a work around for this, but you'll have to give me some time... I'll be able to this in the next week probably... Meanwhile, I just hope someone else can help you. 🙂

---

Is that the db that drives me around the bend or to the light at the end of the tunnel? 😄 lol

Thanks NitinD

Message Edited by Been bitten by LabVIEW on 12-04-2009 09:46 AM

[NitinD]

I'm afraid a CAR db search didn't reveal anything useful. You really need a guy who has been here since LV 7.0. I'll let you know if I find something new.