jgcode

Thanks Val, yes that is correct. Furthermore, nothing was removed in 4.x, in fact that was one of our design goals. Some things were shuffled though to leverage some awesome new features of VIPM (with no affect on relinking of course etc...). Cheers -JG

You can track this bug here: ID: 3386109

You can track this bug here: ID: 3390029

I had this question when I first started using LVOOP and was trying to do some JAVA examples in LabVIEW (where JAVA supports what you are trying to do). Check out the thread, AQ replied - its a good read.

I haven't checked your new script, and this is just off the top of my head, but if the Pre-Build VI saves the Project, does the change persist for that time its run?

No probs, glad you got your script to work - and yes that is correct, those tags are not included if value == 0.

In the video the build script gets run @ 0:30s mark - its when the VI comes into focus (and I hit run but unfortunately it was to the left, offscreen). Typically, you would run a build script like this anytime you want to create a build. The script will handle e.g. synchronizing an exe's version to an installer(s) version or maybe run tests, move files around to handle 2009's new layout and error 6 (which has been fixed in 2011!) etc... 2010 released a feature where you can code pre/post build action VIs, I haven't checked these out in too much detail, and I already used to using a script

[ ] Mmmm..FGPA IDE speed improvements...

Pressing Undo after dropping a Structure places Structure back on Cursor

Replace Missing VI in LabVIEW Project using Palette

Hey Shaun I have an API for interacting with the project, I do similar things with builds for exes and installers so I thought I'd give PPL a go and see if it works. I was able to get it to go however, I don't use the AppBuilder_API (I have never really), instead I use PN's and set the XML tags. You should be able to replicate from this quick video: <object id="scPlayer" width="1150" height="815" type="application/x-shockwave-flash" data="http://content.screencast.com/users/jgcode/folders/LabVIEW%202010/media/37d3ee95-c471-4465-b73f-86cb2417a0c4/jingswfplayer.swf" > <param name="movie" value="http://content.screencast.com/users/jgcode/folders/LabVIEW%202010/media/37d3ee95-c471-4465-b73f-86cb2417a0c4/jingswfplayer.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LabVIEW%202010/media/37d3ee95-c471-4465-b73f-86cb2417a0c4/FirstFrame.jpg&containerwidth=1150&containerheight=815&content=http://content.screencast.com/users/jgcode/folders/LabVIEW%202010/media/37d3ee95-c471-4465-b73f-86cb2417a0c4/Build%20PPL%20Build%20Spec.swf&blurover=false" /> <param name="allowFullScreen" value="true" /> <param name="scale" value="showall" /> <param name="allowScriptAccess" value="always" /> <param name="base" value="http://content.screencast.com/users/jgcode/folders/LabVIEW%202010/media/37d3ee95-c471-4465-b73f-86cb2417a0c4/" /> Unable to display content. Adobe Flash is required. </object>

LabVIEW Spell Check For String Control in Run Time

We tick the Young Alumni Award box, right?

lol

Hi Steve No probs cross posting, it's just considered polite on forums to state that and to include a link in all cross threads so that anyone replying in one thread might not waste time repeating something on another thread; or for readers to find additional information etc... Cheers -JG

Just for fun I just tried your code in 2011 and it seemed to work fine... ...upgrade time.

There is only just a placeholder for the 2011 code up on NI's website at the moment.

[Cross-posted to NI]

Hi Christie Thanks for posting. Following on from Yair, are you able to go into detail on how these VIs differ from the OpenG Variant Configuration API and MGI's Read/Write Anything VIs. Do you have a use case that is not met by the above VIs etc...? Additionally, are you able to post the VIs, they do not seem to have been attached. Cheers -JG

Sorry for the highjacking... but just a note to say that it seems this issue has gone away in LabVIEW 2011 which is good news. And whether others can confirm this.