You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A filter needs to be added to prevent controls, malleable VIs, global variables, etc. from being set as the Top Level VI.
The current proposal is to add an extension check to only allow *.vi and *.vit to be set as the Top Level VI. To prevent global variables, a check for a block diagram may also be added.
The text was updated successfully, but these errors were encountered:
There is a VI Type property that can be used to distinguish between a "Standard VI" and a "Global" or a "Control" along with some other types. Unfortunately, a malleable VI is also listed as a "Standard VI". But a combination of the extension check and type check should do the job.
crossrulz
added a commit
to crossrulz/top-level-launcher
that referenced
this issue
Nov 29, 2024
A filter needs to be added to prevent controls, malleable VIs, global variables, etc. from being set as the Top Level VI.
The current proposal is to add an extension check to only allow *.vi and *.vit to be set as the Top Level VI. To prevent global variables, a check for a block diagram may also be added.
The text was updated successfully, but these errors were encountered: