Jim Kring

There's more to the story.

Yes, I've seen and used the queue data store technique. Mark Balla has put in some effort refactoring OpenGOOP to use the queue data store. I'm not sure when this will be released, but it will happen.

I can't think of any reasons to use the VIT technique. Personally, I did not like it, due to the requirement that the VIT cannot be in memory when it is instanciated. This means that you cannot statically link to it in your application, which makes dependency management in stand-alone application builds more complicated and error prone.

In LabVIEW 8.0, each instance of a reentrant VI has its own front panel and debuggable block diagram. These are referred to as "clones".

Warren, > Seeing as how the last couple of LV beta installations have broken something with the existing/working/installed versions of LV on my machine I'm not sure I'm going to accept though. Get yourself a copy of VMware Workstation or Virtual PC and use a virtual machine as a sandbox for installing/testing the beta. Cheers,

Mike: I've seen this, too. I don't know whether to blame LabVIEW, FireFox, or Windows. The problem seems to come and go. Does it work for you in LabVIEW 8.0? Jeffrey: That's a great idea. Those error clusters take up a lot of valuable space. It might take a =bit of work to exclude these controls, since I am just delegating the task of generating the input/output control/indicator documentation to some built-in functions.

Have you noticed a different between the development environment and the run-time engine (built EXE)? I think I noticed a significant improvement in built EXEs.

Talk about great customer support! Thanks, Darren. And, welcome to the LAVA forums. You get five stars for your first post.

It's a good thing that I only use Build Array in a loop.

Mike: That could be it. FYI -- I've pinged some people at NI about this, too. Hopefully we'll hear back soon.

The Special Characters for Match Pattern documentation states: What does "topic" mean in the above definition. I don't see any other reference to "topic" in the documentation. Does this relate to the algorithm used by the Match Pattern function? Is "topic" a subset of the string?

Off the chart! Woohoo :laugh:

The documentation for the Dictionary library of the OpenG toolkit is generated dynamically. Show the context help for one of the library members and then click on the online help link to open the HTML help in your browser. For extra fun, click on the example links.

Did you see this in the Release Notes? I couldn't find it. Maybe it wasn't considered significant. :headbang:

Thanks, Christian. I did have fun. My wife took me out to a nice french restaurant. I tried sweetbread, which was great until I found out that it wasn't sweet or bread.

OK, it's time to pass the birthday baton... Happy Birthday to Christian Altenbach.

Thanks, Michael. But actually I am only "e"teen years old (that's 0x1E, as I prefer to use the hexidecimal system for keeping track of my age )

That is a great analogy. :thumbup:

That's a new record, I'm sure! Are there any other contenders?

I mean that I don't like that it snaps to grid.

If only that worked for "nudging" with the arrow keys -- I use the arrow keys so often (for small moves) that the snap to grid feature is too much of an annoyance to use.

Mike, You mean, like this? Download File:post-17-1142298891.vi -Jim

You must have DetachableStructurePartsEnabled=TRUE in your INI. <br> Download File:post-17-1142263567.swf <OBJECT CLASSID="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" WIDTH="430" HEIGHT="303" CODEBASE="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0"> <PARAM NAME=movie VALUE="event.swf"> <PARAM NAME=play VALUE=true> <PARAM NAME=loop VALUE=false> <PARAM NAME=quality VALUE=low> <EMBED SRC="http://forums.lavag.org/index.php?act=Attach&type=post&id=2337" WIDTH=430 HEIGHT=303 quality=low loop=false TYPE="application/x-shockwave-flash" PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"> </EMBED> </OBJECT>

You are very welcome. Regarding the errors, please note that the latest version (1.0.5) should fix this problem. I believe that the errors did not have any impact on the mass compile -- but it might still be a good idea to mass compile again.

Version Update: Version 1.0.5 - Sunday, March 12, 2006 at 21:14:08 (UTC) [FIX] Ignores any VI in memory with a Path property value of Not a Path, such as Express VI instances (facade VIs). [NEW] Records the file path of any VI, CTL, etc. that causes an error. Thank you to PJM_labview for making these modifications.