LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Enum not updating case name

I see the behaviour if I right click and edit the enum. But if I close the Test Enum.vi and open it again I do not see the dots.

 

Also if I go to the Enum user event and change the Enum event data node to something else such as Source and then change it back again the dots go away.

=====================
LabVIEW 2012


0 Kudos
Message 11 of 18
(1,532 Views)

"But if I close the Test Enum.vi and open it again I do not see the dots."

 

 

That is what I was doing to get over the issue, I'm working on a large project with a lot of cases in a producer/consumer loop and saving something that is "broken" and hoping it opens back up with all the enums pointing to the right place and having the case structure names correct makes me nervous.

 

The case structure names are missing when the dots are present..

 

stbe solution works:

Only after deleting and re-connecting the wire from the Enum labeled Event Data Node, the coercion disappers and the wire has the correct information again.

0 Kudos
Message 12 of 18
(1,524 Views)
This must be a bug.anyone not seeing this problem, what version are you using?i see it with 2010.
=====================
LabVIEW 2012


0 Kudos
Message 13 of 18
(1,503 Views)

I agree with Steve that this is a bug.  I had not been able to try anything earlier because I was away from the computer with LV 2010.  I see the effect in the Mac version.  Looking at context help over various wires nodes, it appears that the typedef change does not propagate through the Register for User Events or the Event structure until they are compiled.

 

If the system knows enough to "break" the selector labels, it should be able to figure what needs to be changed.  When the typedef is changed, before it is saved or Apply Changes has been selected, the VI is broken.  After Apply Changes, the VI will run again with the coercion dots and generic selector labels.

 

Lynn

Message 14 of 18
(1,475 Views)

Press Ctrl while hitting the run arrow to force a recompile on the VI.  (or just run the VI).

 

It causes a recompile that allows the data type coming out of the "Enum" node inside the user event to be updated.  No need to close and reopen the typedef.

Message 15 of 18
(1,465 Views)

Hello,


I am going to look further into the thread and look into your suggestion that this is a bug.


Regards,

National Instruments
Applications Engineer
Message 16 of 18
(1,435 Views)

Thanks Pat.

 

Please post updates with any CARs--- the behaviour IS odd but .....


"Should be" isn't "Is" -Jay
0 Kudos
Message 17 of 18
(1,426 Views)

Thank you for your feedback. I have looked into this behavior and will report this to R&D.  I will post the CAR information once it becomes available.

 

Regards,

National Instruments
Applications Engineer
0 Kudos
Message 18 of 18
(1,391 Views)