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 support for LabVIEW PPL LabVIEW UIs in built apps #255

Merged
merged 4 commits into from
Aug 9, 2023

Conversation

pbirkhol-ni
Copy link
Contributor

What does this Pull Request accomplish?

This PR fixes the issue in #240 and also partially fixes the issue in #245. It is not necessarily the ideal solution, but it will get customers further than they are today.

  • Modify the Post-Build Action.vi to support copying LabVIEW UIs that are in PPLs. Prior to this change, trying to copy a LabVIEW UI in a PPL would error, which would break your build spec. Note that the PPL must be in the same directory as the Measurement UI.vi.
  • Update the Keysight 34401A DMM Measurement example to use a PPL for its UI. This fixes the issue in Keysight 34401A DMM Measurement UI doesn't work when statically registered #240 and also provides an example for how to use PPL-based UIs.
  • Update documentation.

Why should this Pull Request be merged?

Any reasonably complex UI will require external dependencies. I anticipate this to be a common workflow and we should have a solution, even if it isn't the ideal solution.

What testing has been done?

I tested using standalone Measurement UIs and PPL UIs, both with dynamic registration and static registration.

@pbirkhol-ni pbirkhol-ni merged commit 479da6c into main Aug 9, 2023
1 check passed
@pbirkhol-ni pbirkhol-ni deleted the users/pbirkhol/fix-agilent-example-ui branch August 17, 2023 15:34
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 this pull request may close these issues.

2 participants