[minor] Explicitly Load Plugin Dependencies to Avoid Resaving the Project

[varshini-senthil]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This Pull Request updates the Create Plugin.vi to explicitly load the dependencies of the plugin library VIs before saving the project, ensuring that the dependencies of the VIs are loaded in the project.

Context

• Currently, when creating a new plugin using the Generator tool, the Create Plugin.vi adds the plugin library to the active project programmatically. However, this action does not automatically load the dependencies of the plugin in the project window. As a result, when we close and reopen the project, an * symbol appears in the project window, indicating unsaved changes, which actually point to the addition of the plugin's dependencies to the project window.
• To address this, I have added logic to load the plugin VIs (i.e., the top-level plugin VI) into memory before saving the project. This ensures that the dependencies are explicitly loaded in the project window before saving the project, avoiding the above-mentioned scenario.

Why should this Pull Request be merged?

This Pull Request should be merged to ensure that the dependencies of the plugin VIs are loaded into the project before saving, thereby preventing unsaved changes related to the plugin's dependencies.

What testing has been done?

Manual testing has been conducted by creating a plugin and ensuring that the above-mentioned scenario is not encountered.

[varshini-senthil]

• Dependencies section when a new plugin is created in the project, using the Generator tool.

• Dependencies section on reopening the project window.

[varshini-senthil]

Create Plugin.vi
Code diff
Before:

After: