jgcode

Name: Icons Submitter: jgcode Submitted: 13 Dec 2009 File Updated: 13 Dec 2009 Category: LabVIEW IDE Version: 1.0.0-1 LabVIEW Version: 2009 License Type: BSD (Most common) Icons v1.0.0-1 Copyright © 2009, Jonathon Green; JGCODE All rights reserved. Author: Jonathon Green LAVA Name: jgcode Contact Info: Contact via PM on lavag.org LabVIEW Versions: LabVIEW 2009 Dependencies: No dependencies Description: Discussion contains video demonstration Temporarily located here Installs a range of icons to the LabVIEW Data Directory folder (osdatadir) for use with the LabVIEW 2009 Icon Editor. Icons include icon templates, LVOOP banner and object icons and commonly used glyphs. The LabVIEW Data Directory (osdatadir), by default, is located at C:\Users\(User Name)\Documents\LabVIEW Data for Windows Vista and Windows 7 and C:\Documents and Settings\(User Name)\My Documents\LabVIEW Data for Windows XP. LabVIEW 2009, by default, stores Glyphs in the (osdatadir)\Glyphs folder and icon templates in the (osdatadir)\Icon Templates folder. For this package the installation locations are sub folders within these folders: Commonly used glyphs - (osdatadir)\Glyphs\_glyphs LVOOP Templates - (osdatadir)\Icon Templates\_lvoop icons Icon Templates - (osdatadir)\Icon Templates\_template icons An underscore is used to alphabetically rank the folders, moving them to the top of the list in the LabVIEW Icon Editor. Menu items are also installed for LabVIEW under File >> Icons to open the default folder locations from LabVIEW. Menu selections include: File >> Icons >> Template Icons - opens the (osdatadir)\Icon Templates folder File >> Icons >> Glyphs - opens the (osdatadir)\Glyphs folder This is makes it easy to open and browse all images from LabVIEW. Menu items are installed under (LabVIEW)\Wizard\Icons folder. Installation and instructions: Install package using VIPM. Restart LabVIEW for the Menu Items to take effect. Examples: Open the Icon Editor to view the installed icons Browsw the File >> Icons menu item to open the folder locations from LabVIEW. Known Issues: Due to no support for osdatadir in VIPM and OGPB and the fact that this location is not LabVIEW Versioned, the user should only install the package in one version of LabVIEW. (As of LabVIEW 2009, this is the only option). Acknowledgements: OpenG ICON Technologies Version History (Changelist): 1.0.0-1 2009 12 05 [New] Initial release of the code (LabVIEW 2009) License: Copyright © 2009, Jonathon Green All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the <organization> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY <copyright holder> ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <copyright holder> BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Support: If you have any problems with this code or want to suggest features: please go to lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the LVOOP Custom User Scripting support page. Distribution: This code was downloaded from the LAVA Code Repository found at lavag.org Click here to download this file

Cool!

No dramas, You pick stuff up as you go, always heaps to learn with this stuff.

The code was originally done in 8.5 or so and I recompiled it in 2009. Regardless of the recursive method used, it still works, which is the most important thing.

Hi Ryan Use the Text - Scroll Position property node to move the scroll position. In order to get a reference to a VI in memory... The other way would be to check for an error returned from the Open VI Reference function if the VI is not in memory. It's up to you. Cheers JG

No probs, If forgot to say awesome effect too!

Cool, glad it was an easy fit My suggestion is that you do not open the window (but don't close it either!) at the start. Run your code then at the end open the window Remember the way it is coded - the save method only runs if the Project Path is valid. If you are calling it as a tool then this will most be likely empty as you have no default. Therefore if you call the close method and you have not saved the project you will lose it! Cheers JG

Hi Norm I know there is one in OpenG but your get parent ref is missing from the dist in case you meant to include it. <userlib>:\FRSE Tools\AppControl\Tool - Get Parent.vi Cheers JG

Sweet! Well done mate!

I did notice that when I immediately replied, instead of creating a double post it merged the posts into one, attachments and all. That was cool, but only works if no one has posted of course and you want to extend your attachments not edit them. This problem is really annoying - is a Admin able to comment about a fix please? Cheers JG

Hey man go for it! At the end of the day a reference is always nice but this one is not mine I got it from a course - so there is a reference in the VI description that you should include! Its just an example and not going to be 100% so you will need to do some work. If I remember correctly you need to handle cases where the folder already exists (which should be ok if you always use it for a new project) and adding a project library causes an error as it tries to add VIs twice! Additionally you may like to check out my build script (link in my signature) - it has some VIs that do work on a project. I would be interested in seeing your example when you are done!

Hi Eric What do you have in mind? You can manipulate the project through the Project Class (VI server) using property nodes. Here is a snippet to add a folder to a project. I have attached an example (I did on a course a while back). Might get you started! Create Project.zip [LabVIEW 2009]

Hi Thomas A Value Change event is not fired by a control when you programmatically write to it (unless you write to the Val(Sign) property). If you change your "Event" Switch to a control (from an indicator), disconnect the logic and run your VIs your code will work when you manually change the state of the Switch! Additionally you may like to put some timing in the subVI.vi's while loop - unthrottled loops hog CPU resources. Cheers!

There is an appendix at the back on OOP which walks through FGV then GOOP. It is a great introduction to the concept of OOP in LabVIEW and well worth reading. There is no LVOOP in the edition I have tho.

Cool! Thanks Michael

Thank you

...but you like to use them in your code

Thanks Mark No rush, I just wanted to check I had followed the process correctly. Thank you for your time.

Sorry, I meant for Machine Access, you were talking about Exported VIs!

Yes, localhost works as well.

(This is my first time - be gentle ) Dear Mod I want to submit this code to LAVACR certified. I did so at start of week but haven't heard back from a mod yet. I did the Report to Moderator but I think I faff'd it as I did not include my username and title!! If everyone is busy that is cool. I just wanted to check as the Report to Moderator button is now gone so I can't redo it! Any help will be appreciated. Thank you JG

Not something I use alot, although I like using them when spawning a daemon process aka 's Endevo GOOP Active Object template by Kurt Friday (Sciware) I copied investigated the framework for native functions (LVOOP SEQ pre 2009 and DVRs) It works great. Does anyone use them a lot?

Depends where you host it I guess. If you submit it to LAVACR is says no password protected VIs. I always like to see what people are doing (hint: please do not PP ) But does the NI forums have any rules on this? As I know Darren has mentioned that he has had to in the past.

You could also use an occurrence. In that case, due to the lack of error-in-error-out to sequence it to the waiting while loop, you could use a flat sequence structure or artificial data flow. Don't know which people would consider neater or better between the semaphore and occurrence...I have not received that memo