03-31-2026 11:31 AM
NI has added an item to <vi.lib>\event_ctls.llb\lveventtype.ctl
2025 version:
2026 version:
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.
03-31-2026 11:57 AM
It feels like the same bug where if you add an item to the middle of an enum, LabVIEW sometimes gets confused.
03-31-2026 03:14 PM
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.
03-31-2026 03:22 PM
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.
03-31-2026 05:01 PM - edited 03-31-2026 05:08 PM
@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.