What would cause a enum typedef constant changes during execution

[ggaryt]

Hello,

In my program I having a problem with an enum constant for a tab selection changing value at runtime.  The enum is in the initialization part of the program and when I single step through the loop you see the tab property node for the value highlight and then in the next step the enum changes value.  I'm running LV 8.0

Any information will be greatly appreciated.

Gary

[Ben]

Never seen or heard of such a thing.

I suspect the enum is a contreol indicator and the property nodes is for it and not the tab.

Can you post some screen shots that show this.

Have you reacreated and replaced the enum constant?

Ben

[ggaryt]

I'm not sure why this is happening but here are the screen shots of me single stepping through the loop that has the control in it.

[Ben]

Please post pngs.

Docs no-liked inside fence.

Ben

[ggaryt]

What?

[Ben]

I am on-site inside a govt facility where i would be escourted out within minutes after big brother detecting me down loading a ".doc" file and opening it.

After I served my time in jail, I'd have to come right back here to install all of the software that was wiped out when IT reformatted the machine I am using.

So please post

.png

or

.jpg

Files,

Ben

[cancancanopen]

What is there in the true case extreme left of the picture in the doc, have you used the enum twice in that case itself,

use search for instances to find out.

[tbob]

The .doc document clearly shows a constant's value being changed.  This seems impossible.  It's not a variable, it's not a property node, it's a constant that has been changed.  Something very wrong here.  You can't change a constant programatically.  You may have a corrupted VI.

[ggaryt]

No I haven't used it twice in the case statement, that case statement you see to the left is a reset a local variable Boolean from true to false.

[ggaryt]

Ben,

Here are three jpg's to view with the first one once I enter the loop, the second is single stepping up to the property node and the third is the next single step  and where the constant changes.  I hope this helps I'm looking into a possible race condition could be the cause of this, but I'm not sure yet.

Gary