LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

why is value(signaling) not working for typedef enum

I am trying to signal a value change for a enum typedef but the signal dose not work.  I am using LV7.0.  Is this a known limitation, bug or is there some logic error on my part.
 
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 1 of 6
(3,038 Views)

Wow, I've never seen that one before.  You're right, the Value(Signaling) property does not appear to fire the Value Change event for a Typedef Enum in LabVIEW 7.0.  I tried the same thing in LabVIEW 7.1 and 8.0, however, and it worked fine in those versions.

-D

Message 2 of 6
(3,029 Views)
Guess I will have to upgrade.  I cant live without my typedefs, they make code maintenance possible. Bummer
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
Message 3 of 6
(3,020 Views)

In the spirit of bug reporting that has been recently instituted on the forums, I just found the reference number for this issue (32682QPR) and confirmed that it was a bug in LabVIEW 7.0 that was fixed in 7.1.  The only workaround offered in this bug report was disconnecting the control from its typedef.

-D

Message 4 of 6
(3,014 Views)

Unfortunatly disconecting from the typdef will not be an option during development since I use typdefs to encapsulate structures which I change while developing the code (add or change fileds as needed).  If I create a dynamic event which uses the same typdef do you know if this work around works: make a dynamic event which uses the same typdef and generate a user event inplace of a value signaling essentially doing the same (although complicated the code a little).  If not I will have to upgrade.

Paul

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 5 of 6
(2,996 Views)
I ran into a similar problem some months ago with a cluster indicator, but as I wanted to control the event more closely, I soon got rid of the value change event and entirely relied on the user event.
The event handler had to heavily manipulate the changed indicator, so I defined as data type a reference to the indicator itself.
If I correctly remember, every time I changed the typedef (not many, happily), I needed to "recreate" the user event (typically deleting some wires, then rewiring).

Paolo
Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 6 of 6
(2,978 Views)