AutoMeasure

Hi. Blocks the user interface thread? Not sure what you mean. But anyway if you call the One Button or Two Button Dialog in parallel with the rest of your Labview code, then your code should continue to execute and update visible VI panels. You can make a little pop-up manager with a parallel while loop, and use local or global variables, events, or synchronization functions to command the pop-ups from your main code. Were you asking how to make your own custom pop-up? You know that one VI can call another VI like a subroutine, with inputs and outputs, right? Just make a separate subVI whose panel is just what you want the user to see. Put the controls and indicators you don't want seen, particularly those wired to the connector pane, out of view off to the side. Configure this subVI to "Show front panel when called" and "Close afterwards if originally closed." You can also configure centering on the screen, displaying menu bar and scroll bars, etc. Have fun experimenting. Good luck.

Hi, Thomas. Thanks for trying out the bug. I made another VI that does not use the Unflatten and posted it as a new topic.

This is a Labview 8 editing bug along the same lines as my previous post. I made it a new topic because it is a different VI attachment. Please read the note on the VI diagram. Thanks for trying it out. Download File:post-3297-1130164281.vi

One of the things I wanted to check with Labview 8 is whether or not NI fixed problems in which Unbundle and Bundle By Name can change cluster elements during editing, such as when rewiring, adding structures, or reordering the cluster. I found that in 2 out of 3 situations, Labview 8 did the right thing while Labview 7.1 did not! The one situation I see where a problem still remains is demonstrated by the attached LV8 VI. Please see my note on the diagram. Thanks for trying it. For many years I've seen problems (although rarely) with using sub-clusters and Unbundle By Name using the dot convention to denote cluster levels. At times, unbundle elements would change with no apparent causal action on my part. Has anyone else noticed that? Download File:post-3297-1129928531.vi

Hi, wireheads. I'm new to this forum, and I'm happy to have heard about it and to start using it. I'm looking forward to LV8's arrival. I've been hearing about the project structure and related VI name issues. Is the following old problem addressed in LV8??? When you're not in the lab, someone opens your many-layered Labview program while another Labview program is in memory. The two programs share a common subVI, but the other program's subVI is an older version that works differently although it has the same connector pane. The user makes a cosmetic change to your front panel and saves it, inadvertently also saving the path to the wrong version of the subVI. Later, you come in and build an EXE, not realizing that your code is compromised. A more insidious form of this problem was when there are no other programs open, but the wrong-version subVI is in the Windows clipboard. When you open your program with a subVI of the same name, the path to the subVI is changed to the path of the one in the clipboard. One learns to be excessively organized with version control, directories, naming VIs, emptying the clipboard, and opening LV programs. Thanks.