LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Event "Type" enum issue with 2026 RTE

NI has added an item to <vi.lib>\event_ctls.llb\lveventtype.ctl

2025 version:

2025 type enum.png

2026 version:

2026 type enum.png

I have an application that uses the Value Change item as a case structure case. If the application is built in 2025 with "Allow Future Versions..." checked and 2026 RTE installed, the case no longer executes because it seems to be wanting the 66 value but is getting 67.

 

I attached a minimal project that exhibits the behavior and if I don't hear it's already a known issue I'll submit a bug report. Hopefully it is not too late to move the new "URL Change?" item after the previously existing ones.

0 Kudos
Message 1 of 5
(454 Views)

It feels like the same bug where if you add an item to the middle of an enum, LabVIEW sometimes gets confused.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 5
(437 Views)

That's a weird one, because the indicator is showing that the enum is returning 'Value Change', but that's not the enum case that is executing. I have filed Bug 3806386 on the issue.

 

Also, R&D keeps that enum list alphabetically organized, that's why the 'URL Change?' item wasn't added to the end.

Message 3 of 5
(400 Views)

Interestingly, if I add a case for every enum value to that case structure (i.e. I get rid of the Default case), then the proper frame executes when the EXE is run with the 2026 Q1 RTE.

0 Kudos
Message 4 of 5
(398 Views)

@Darren wrote:

Interestingly, if I add a case for every enum value to that case structure (i.e. I get rid of the Default case), then the proper frame executes when the EXE is run with the 2026 Q1 RTE.


In the IDE this would be a compile error upon opening in 2026. So maybe the VI should be broken in the exe? It seems like undefined/dangerous behavior when the enum is not compatible with the case structure.

0 Kudos
Message 5 of 5
(379 Views)