Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a filter when setting the Top Level VI #16

Open
crossrulz opened this issue Nov 18, 2024 · 1 comment · May be fixed by #21
Open

Add a filter when setting the Top Level VI #16

crossrulz opened this issue Nov 18, 2024 · 1 comment · May be fixed by #21

Comments

@crossrulz
Copy link
Contributor

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.

@crossrulz
Copy link
Contributor Author

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
@crossrulz crossrulz linked a pull request Dec 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant