This tool is provided as an example to the LabVIEW user community under the Sample Code License (ni.com/samplecodelicense). It is not a National Instruments product and not supported through the regular support channels. Please leave questions and feedback about the UI Manager in the comment section below and rate the document. Please provide suggestions for new features and improvements and related use cases.
The VI Package is built using VI Package Manager 2017. You can get it by installing LV 2017 or by downloading VIPM for this page - https://vipm.jki.net/
User Interface Manager is compatible with LV 2016 or later.
This tool is designed to help programmers capture and apply complex UI configurations to any LV VI, both at edit and run time. Using the User Interface Manager Tool and its API, you will be able to configure your UI, capture that configuration, export and import it from XML file, and apply any previously captured configuration. Using this tool you can separate the configuration of your UIs from your application functionality and still be able to achieve any effect as you would using standard VI Server methods and properties.
If the user interface property you want to capture is not handled by the standard provided UIPs, you can create a new one, using the UIP Class Template. By providing your own implementation for five simple methods, you will be able to capture any property from the controls on your VI front panel.
This tool has not been tested on LINUX RT with UI.
Some of the use cases that can be handled by this tool include:
Currently available User Interface Properties (UIPs):
Example additional UIPs (in ZIP archive):
The package provided below, installs the UI Manager API to be used programmatically in your applications and the UI Manager Tool in the LabVIEW Tools menu, which allows you to capture UI states interactively in a user friendly way.
- Increased performance of the UIM Tool when working with big projects by limiting the number of memory scans for open VIs.
- Added new functionality for specifying the UIPs used by UIM. Now the UIPs are specified within the XML itself in the UIPList tag. If no UIPList tag is specified in the XML the default UIPs and the Plugin UIPs will be used. If the UIPList tag is specified then only the specified plugins will be used.
- Flatten and Unflatten from String XML functions added to make it easier to specify the UIM strucutre in code, by string.
- Save XML function modified to generate Pretty Printed files.
- New ValueUIP supporting: String, Numeric, Boolean, Slide, Knob, TabControl, Path, Enum, Ring. The parsing of these values happens while getting and setting the values. Because of this they are a little slower than other properties. Use with caution.
- Included example about the ValueUIP
- Updated interface for adding new UIPs to make it easier to use in executable.
- Filtered the list of VIs in memory to only the ones that have FP open and valid (UI Manager Tool).
- Reformated some of the interfaces of the UIP related methods.
- Added to Capture State checking for duplicated label names and returning error in that case.
- Added detailed description link to UIM community web-page to VI and tool.
- Added right click menu to controls on the FP to capture state from only specified controls on right click.
- Corrected bug that would cause crash in different LV versions when using the UIM.
- Rearranged some of the functions and API to work easier and less error prone with inbuilt UIPs.
- Removed project from package not to confuse users
- Added a plugin UIP folder handling. The folder location is <User Documents>\LabVIEW Data\UIP
- Removed the compiled EXE version of the example because it caused confusion
- Changed the behavior when user wires CTL reference into Apply or Capture method. Right now the behavior is that the wired references are used and the VI is not traversed for references. This improves performance in big applications, by specifying up front, which CTL refs to use.
- Updated the examples with more descriptive names. Modified one example to show how an app with UIM API can be built into an executable.
- Removed the requirement for other packages to be installed with this tool. Now it is an independent package. Removed some small errors related to running the tool from the menu.
- Due to unforeseen bug while loading had to revert back to LV 2016. The package is again only available in LV 2016 and higher.
- Includes a QuickDrop shortcut for capturing the UI state into an XML file. Now, to capture state of the UI you just need to press Ctrl+Space Ctrl+U. The file generated this way will have the same name as the VI and the extension XML. It can be then loaded using the API or the UI Manager Tool from the tools menu.
An additional option you can use is the <Ctrl><Shift>+<U> which will take the text from the QuickDrop ComboBox and use this text as the UI state name.
Figure 1: Main window of the UI Manager Tool
Figure 2: UI Properties specification pane in the UI Manager Tool
Figure 3: Function palette for the UI Manager showing the API functions
Figure 4: Example of programmatically setting the UI configuration using the UI Manager API
Figure 6. XML representation for the UI Manager
Please provide comments, feedback and feature suggestions in this forum post: http://forums.ni.com/t5/UI-Interest-Group-Discussions/Feature-suggestions-for-User-Interface-Manager...