Ton Plomp

I would want to track certain users (me for instance) via an RSS-feed, via this I can easily track in which threads I posted recently and see if there are any updates. Ton

When I look at the LAVA page I have several options for RSS feeds to subscribe to that are empty: Lava Community blog feed (http://lavag.org/rss/blog/) Articles (http://lavag.org/rss/ccs/1-articles/) Media Demo New features (http://lavag.org/rss/ccs/2c9-new-features/) Media demo - other (http://lavag.org/rss/ccs/2c10-other/) Report center RSS feeds (http://lavag.org/index.php?app=core&module=global&section=rss&type=core&member_id=2399&rss_key=a6e1bb31db3901678f095f895be06880) Is this intentional? To

Or is the bug the behaviour of the actual 'Replace' action? I can see how the fix could be the default behaviour for 'Replace'! (or is it a big no-no in computer science) Ton

NO! If you program in such a way that the wire before the +1 primitive isn't branched at all the LabVIEW compiler will reuse that memory location. Likewise it's important to remember that if you are adding a scalar and an array using the '+' primitive you need to wire the array to the upper input of the +, the compiler tries to use the same memory location for the output as for the upper input (-/* likewise). Ton

I've been thinking a little bit more about this, and I would say it's pretty good doable! We should deprecate all of our current VIs and we should add some things to our deprecation process: -Each VI that is deprecated should have a boolean tag 'Deprecated ==True' -If a VI is deprecated there should be a relative path tag 'Replaced by' that contains the path of the VI it's replaced by. Now we could write a tool that goes over all the VIs in a folder or hierarchy to update the code to the latest version. Ton

In theory: YES I would opt for a library name with the following naming theme: OpenG.String.lvib, on the actual VIs we could lose the name mangling (__ogtk). Now for real, I think this is a hard one to do. It would mean deprecating all of out VIs and wrapping them in complementary libraries. Our could we hack some update code in congregation with NI? I think it's doable to write some 'wrap and deprecate' tool to do this and regenerate our palettes.I wouldn't want the polymorphic VIs to be public and make the specific instances private, main reason is that Real-time cannot cope with variants, and you couldn't bypass the public polymorphic VI by calling directly into the specific instance you need. Ton

The Boolean XControl has a font-dialog that only works on Windows. However you can make it work on other OS's, it only needs a list of font-names. Ton

What happens a 3. is that by placing all the VIs in the library the canonical names (not paths) of the VIs are altered. LabVIEW basically relies on VI names (not paths). You did this with the functions calling into these VI in memory, LabVIEW can detect this and probably showed a dialog 'foo.vi is being altered do I need to check out?' (or you disabled this option in the SCC options dialog. You didn't check out, but you couldn't save your changes. If LabVIEW tells you you need to save, you probably do, it's pretty good at this. (at 4. you actually had to save). So any VI linking to a VI moved into the library is looking at the right spot for the wrong VI. The easiest way to fix this is by manually opening the VIs and select the VI you need. Ton

I've developed one myself and it isn't ready for general public (might never be). There are some basic functions that needs to be included before I can publish this. Ton

No you don't have to! I was worried about this as well, but it turns out that the combo-box constant is a sub-class of string constant (which you are registring for), so the tool keeps working the same way! It might be nice to set the checkmark if the string constant is a combo-box so the drop-down list gets updated when running the State Editor. Ton

Feature request: Optionally change the constant into a ComboBox constant: <object id="scPlayer" width="225" height="290" type="application/x-shockwave-flash" data="http://content.screencast.com/users/TonPlomp/folders/Jing/media/1248a53e-b04e-4b98-a790-d3a3732d611e/jingswfplayer.swf" > <param name="movie" value="http://content.screencast.com/users/TonPlomp/folders/Jing/media/1248a53e-b04e-4b98-a790-d3a3732d611e/jingswfplayer.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/TonPlomp/folders/Jing/media/1248a53e-b04e-4b98-a790-d3a3732d611e/FirstFrame.jpg&containerwidth=225&containerheight=290&content=http://content.screencast.com/users/TonPlomp/folders/Jing/media/1248a53e-b04e-4b98-a790-d3a3732d611e/State-dropbox.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/TonPlomp/folders/Jing/media/1248a53e-b04e-4b98-a790-d3a3732d611e/" /> Unable to display content. Adobe Flash is required.</object> Here's the code I used in the JKI state editor: Ton

I have a tool that acts like a pre-build tool, and after that calls the NI-builder. Ton

What SCC are you using? If you use the integrated SCC provided by LabVIEW you can alter those VIs (vi.lib/sourcecontrol/providers) to actually store the parameters, however there is a small glitch: the LabVIEW SCC interface doesn't know which LabVIEW instance is actually running... Ton

Move the VI into a lvlib, you can use the verions of the lvlib as the actual plugin version. Ton

I can see your point, however how likely is it that you don't know by forehand wheter you have large attributes (thus need the enumeration) or have large attribute-names (thus need indexing)? If you develop your code you'll probably know which one of the two is most likely, or you could add an attribute called 'Style' that tells the code to either index or enumerate. However you can index attributes, by placing the attribute inside a variant inside an attribute, this attribute gets a short name. The footprint will reduce however but will be dominated by the size of number of variants. One other question, have you also played with small attributes with long names (the inverse of the first case)? Isn't it possible to use the 'Get attributes' without a name, but with a type (thus eliminating the 'variant to data' for the first code)? I think it is possoble, or should be in the LabVIEW Idea Exchange. Ton

François, could you alter the set to move the boolean text ouside of the boolean image? I have created a screencast on this issue. <object id="scPlayer" width="632" height="323" type="application/x-shockwave-flash" data="http://content.screencast.com/users/TonPlomp/folders/Jing/media/ecf08f20-602b-446c-8a5e-73f7e46c7ce7/jingswfplayer.swf" > <param name="movie" value="http://content.screencast.com/users/TonPlomp/folders/Jing/media/ecf08f20-602b-446c-8a5e-73f7e46c7ce7/jingswfplayer.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/TonPlomp/folders/Jing/media/ecf08f20-602b-446c-8a5e-73f7e46c7ce7/FirstFrame.jpg&containerwidth=632&containerheight=323&content=http://content.screencast.com/users/TonPlomp/folders/Jing/media/ecf08f20-602b-446c-8a5e-73f7e46c7ce7/2011-03-28_1540.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/TonPlomp/folders/Jing/media/ecf08f20-602b-446c-8a5e-73f7e46c7ce7/" /> Unable to display content. Adobe Flash is required.</object> Ton

What about conditional disable structures? They should nowadays offer the functionality that you packed into the OGP installer. Ton (PS Welcom to Win7, it is superb to XP)

Event structures are always active. They may not be executing, but if you have an event configured to 'Lock panel during execution', it will lock as soon as the event happens, this is by design. One of the examples why this is necessary is a convoluted state machine where the event structure only executes every 5 seconds, and you have a mouse down event for a picture. Let's say that executing of this event takes 2 seconds. Now if you are in bad luck (or your users are impatiently), you can get numerous 'mouse down' events during the 5 seconds loop effectively killing your app (every event takes 2 seconds in which new events are started... Ton