Francois Normandin Posted January 11, 2010 Report Share Posted January 11, 2010 Name: UI Tools addon: Tree & Tagging Submitter: François Normandin Submitted: 10 Jan 2010 File Updated: 16 Feb 2010 Category: User Interface Version: 1.0.4 LabVIEW Version: 8.6 License Type: BSD (Most common) UI Tools Tree OOP Add-On v1.0.4 Copyright © 2009-2010, François Normandin All rights reserved. Author:François Normandin Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 8.6 Dependencies: lava_lib_ui_tools >=1.0.36 Description: This package contains classes for manipulating Trees with some enhanced features. It consists of a set of VIs to create tree objects and associating tags with data in a variant format. Includes: - includes some icons from FamFamFam (see license in _Symbols directory) for demo purposes. You do not need these icons if you use the Tree OOP classes in your work. Instructions: After installing package with VIPM, refresh palettes if VIPM is not set to refresh automatically. You will find the palettes in the UI Tools functions palette (user.lib) Known Issues: - No drag and drop functionalities included. You'll have to do that on your own if wanted. (for now anyway) - Arrays will be shown has a succession of Unnamed items. Recursive VI provides a way to put it on a single line within brackets, but has been removed to provide backward compatibility to 8.6. An add-on will be posted for LV 9.0+ users. - The Children & Parents Symbols synchronization works only for Symbol indexes 1-2-3 (True-False-Mixed). - When adding an item on the same level as an existing one, it gets added in front. Expected behavior would be to have it added afterwards. - Modifying a child's data does not recursively modify the parents' data (cluster variants). This will become obvious once you try the framework... This functionality will be kept in my mind for future improvements. Acknowledgements: Norm Kirchner from which I got some tricks in his Tree API (see LAVAG.ORG) Change Log: v1.0.4: Solved problems with hardcoded path for symbols installation. Affected primarily installations on 32-bit Windows systems. v1.0.3: Initial release of the code. (LV 8.6) License: Distributed under the BSD license. Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to the discussion page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org ============================ Click here to download this file 1 Quote Link to comment
Mark Balla Posted January 24, 2010 Report Share Posted January 24, 2010 Certified 1-24-2010 Moved to UI Group Quote Link to comment
Stobber Posted August 27, 2012 Report Share Posted August 27, 2012 I just installed this package into LV 2011, and the palettes weren't shown anywhere. VIPM couldn't find them, either. I looked around and found all the code and the .mnu files in <user.lib>\_LavaCR\UI Tools, so I just manually added functions_lava_lib_ui_tools_treeoop_addon.mnu to my palettes. It looks like this UI Tools addon needs to be coordinated with the others so each can safely install its own palettes without stomping on anyone else's. Very nice tool, by the way! Quote Link to comment
Francois Normandin Posted August 27, 2012 Author Report Share Posted August 27, 2012 Hi Stobber, I refactored the UI Tools but not the addon modules yet. I'll check to see if I can get a new installer to change the location of the palette of these addons. thanks for the feedback Quote Link to comment
Francois Normandin Posted September 7, 2012 Author Report Share Posted September 7, 2012 Update... To add the addons under the "LAVA>>UI Tools" palette, I've needed to create a UI Tools palette package that will install through LVTN. My submission has not been done yet for this addition, so it will be a while longer before I post an update for the Tree-Tagging addon. Failure to do so would cause multiple UI Tools palettes to appear side-by-side in the LAVA palette, which is terribly bad style . The good news is that is works well and will allow me to integrate more addons that way in the future. I'll be reviewing all the comments I got on this addon, make modifications and tests, and I'll submit it whenever I'm through with the LVTN submission. Since your solution works in the meantime, I'll leave it at that for now. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.