dannyt

HI I notice that with most of these VI you have allow the caller to pass in the tree reference or use the internal get current VI to find it, you use the same approach for the item tags. Other than the consideration of "data flow" is there any rewason to favour one method over the other, ie pass things round or leave the VI to figure it for themselves ? cheers Dannyt Another option to add to API. Item Modify Cell Color.vi

Hi I would just like to say I have only started working with LabVIEW tree's for about a week now. I have found this API to be a really great place to start would highly recommend it to anybody. So from me much Kudos and thanks to Norm. cheers Dannyt PS I do not know if you want to add this VI to it next time you up-issue. Tree Expand Item.vi

Two questions. One, when you close the VI and get the prompt to save it what does the List Unsaved Changes link show in the "Explain Changes" window, also does this happen if you one that single VI up on it own directly. Dannyt

Bruce, many many thanks to you for that, works a treat, +1 rep to you sir :-) LAVA to the rescue again. I was at least please I was heading onto the right lines NOTE for anyone else downloading the 8.0 version, you file Create Shortcut.vi has the 8.5 version of Set Shortcuproperties in it so remember to put the new 8.0 one in its place Dannyt

I will have a look at IShellLink thanks. I was try to avoid a thirdparty option if possible and just do it with LabVIEW so I did not have to deploy anything out with the LabVIEW. Maybe there is a registry key ? If I was going in the thirdparty direction I could code up a WSH example myself 'Create a Desktop ShortCut set WshShell = WScript.CreateObject("WScript.Shell") strDesktop = WshShell.SpecialFolders("Desktop") set oShellLink = WshShell.CreateShortcut(strDesktop & "\Shortcut To Notepad.lnk") oShellLink.TargetPath = "Notepad.exe" 'WScript.ScriptFullName oShellLink.WindowStyle = 1 oShellLink.Hotkey = "CTRL+SHIFT+N" oShellLink.IconLocation = "notepad.exe, 0" oShellLink.Description = "Shortcut To Notepad." oShellLink.WorkingDirectory = strDesktop oShellLink.Save cheers Dannyt

Hi I wonder if anybody could give me pointers in creating a Windows XP desktop shortcut with LabVIEW or how edit an existing one. Working in LabVIEW 8.2.1 I can see how to do this with WshShell commands (the Windows shell scripting environment) but not with LabVIEW. I did try playing around with the "IWshRuntimeLibrary.IWshShell2" ActiveX object but though I can find a CreateShortCut invoke method I seem unable to do anything constructive with it. cheers Dannyt

Thanks for the post to this App Note I found it an interesting reading. Does anybody know if the part 2 of 2 ever get written and if so does anyone have a copy of it or a link to it please ? Dannyt

I am sorry but I do not understand your question, I can open and edit your VI OK, though there are lots of missing subVI's, that you have not included. Could you please explain what your actual problem is in more detail, that way somebody may be able to help Dannyt

Hi, I have been playing with your build script and I really like the potential of it. Unfortunately our code base is written in LabVIEW 8.2 and I have been playing around trying to get the build script working in 8.2, so this is just a quick not to anyone who may be interested, the build script CAN be run when saved back to LabVIEW 8.2.1, but the project must be closed for it to work. It appears in LabVIEW 8.2.1 the call to AppBuilder\BuildTargetBuildSpecification.vi will fail with an error 1025 if the project is open. However close the project and the call works. Extra note in LabVIEW 8.2.1 if you open the project then open your build.vi and close the project, the build.vi VI will also close. So first ensure that your project is closed, open your build.vi and run it. cheers Dannyt

I have written a little utility that does some of this. Our process is (using ClearCase as our SCC) to check out and make changes on all files that we are really changing and then check those files back into the SCC, ignoring the recompiles. So if I then load my top level VI I get a sometimes very long list of files that need recompiles. With the top level VI open I run a tool that finds all VI with unsaved changes in memory, I stumbled upto a property node "VI Modification bitset" , I then automatically do a ClearCase checkout of all these files, re-save them and do a ClearCase checkin with a common checkin comment like "File has been automatically update due to recompile". Dannyt

wow 1K posts that's really impressive and as others have said there has been some useful stuff in those posts so thanks for it all Dannyt

One more option I forgot the mention, is here on LabVIEW, I have just started playing with jgcode's Build Script it runs in LabVIEW 8.6, I am trying to get it working for myself in LabVIEW 8.2.1 and from the little play I have had with it so far, I could be a pretty powerful tool. Dannyt

Damn, so far in my life I have managed to avoid becoming a twit or twitter (what is the term for somebody who reads twit's ?), but people seem determined to try and drag me into the next centry, will it work Ok with my IE6. For an old lag like me it is very confusing do I take my LAVA via Twitter or maybe the RSS Feed or maybe the LAVA Facebook or shall I just keep on reading the good old web site itself. Actually I think I will just wait for the DVD to come out

:thumbup1: Yes I am with you on this on Jim, I would like the search / find improved in so many ways Dannyt

Not sure ....... how fast do you normally move ?

(my answer also cross posted) The answer to your prayers lies in the OpenG builder it is part of the OpenG software tools, also search for the OpenG builder of Lava there are quite a lot of references to it I have been using the OpenG builder for a couple of years now and one of the major advantages it gives is methods to run pre and post build scripts and also plugin scripts during the builds. We control our VI's within ClearCase and using the OpenG builder I can automatically set the correct configuration specification before a build and check out a revision file and some other stuff. Also during the build I can generate a BOM list (Bill of Materials) and after I can automatically check the built file into ClearCase if I want. I will say it is not without it's own little niggles, it builds slower than the normal NI build for example, but for now it will provide what you are looking for. cheers DannyT

I'm still trying to turn my hand over the correct way

Could you tell me which version of LabVIEW this has been built for. Thank you Dannyt

Hi Sharon, Well that was fun, I have a solution for you, I am sure others will give you a better one. Basically your VI object Class needs to be a ControlTerminal in this case and not Numberic, note the attached file picks up Diva.vi from C: not D: Though this change works I think you need to be a little more generic in your code. The Diagrams[] returns an entry for each case in your case structure, I would make it loop round for each case, and then use a Diag - AllObjs[] on each of these Diagram, you then need to go through all the objects in that Diagram. An alternative way of going about this especially if you want to make this a more generic tools is to use the TRef Traverse for References.vi as you starting point. 01Case.vi

I like and use Bugzilla myself, it is quite easy to install and set-up Have a look at Lava Issue Tracking Tools thread Dannyt

I have been into my daughters primary school a couple of time and I taken the old Lego Mindstorm kit. I had made up two small robots both with tank tracks drive, one a simple line follower and the other with touch sensors and arms so when it touch something it would stop move backwards turn around and go somewhere else. The kids year 2 so about 6-7 loved them and I got plenty of questions. They especially seemed to enjoy it when the line follower failed to follow the line very well and kept wandering of the line randomly. The very hight level of fluorescent lighting from all angles mean there was very little contrast unlike my living room floor. So we play with turning the light off, then on, then in front of the windows or not. I actually pick ed up an old Mindstorm kit of Ebay to do this was only about £50. Dannyt

First thanks for this I found it very interesting, I do really need to spend some time looking more at LabVIEW OO and start doing some.... .... however ..... please please please , why can NI not make this type of thing in a downloadable form, am I being silly is this not possible with webcast ? This is not the first and I am sure not the last really good webcast / video presentation I have come across on the NI site, that I have though wow what a great and useful presentation and I really want the opportunity to view them several times and at time when I have a bit more peace and quite. Also I have on several occasions tried to find a previous webcast /video on the NI site that I rememberer and find the links are not longer valid and I cannot find it. dannyt

ah the afternoon shift has now arrived :-)

This appealed to me, nice seeing all the people NOT taking the escalator linky (not sure If I can the the embedding working

Congratulations Jim :thumbup1: Dannyt