Jim Kring

Mike, Are you sure that "mike", "elise", and "jennifer" is a contiguous group? What happens if you add "matthew" ?

The search for meaning within the avatar will bring you to the realization that the meaning is within the avatar itself. It is amazing how one will go to an array of lengths to find sum divisive meaning. If it is not a play on words then what is the hidden code.

Maybe it is because you can (roughly) find the letters of your name (JOE) in the image:

FYI - the CAR ID for this bug is 3RK9A23A.

FYI - the CAR ID for this bug is 3RRG36V2.

Use the Scan From String function: Download File:post-17-1133283770.vi

Here is the response from NI Support

Dan: I also use SnagIt. It looks like you did have some trouble with the screenshots, because they didn't appear in your posting. Take a look at this posting called "How to Insert Images in your Posts, Making a good first impression." This will give step-by-step instructions with illustrations.

Slashdot >> Windows Vista May Degrade OpenGL

David: you got wrapper VIs? Lucky! I worked on an Aerotech stage that came with a "LabVIEW Driver" which consisted of "naked" calls to DLLs strewn about the block diagram. To make matters worse there were many instances of the "home brew sequence structure" (For Loop + Case Structure = Sequence Structure). Sequence Structures are bad enough, but then you have to deal with a custom implementation :headbang:

Hmmm, what does your avatar mean? Does it mean an array of DBLs? :laugh:

I've opened a support incident with NI. I'll post the CAR number any other useful info here, once it's available.

AutoMeasure: I just tried a build an your XControl does not work in and EXE I have attached the EXE and lvproj with build spec's. Download File:post-17-1133039560.zip

WARNING: This bug will crash LabVIEW See the attached document for images showing important steps. Download File:post-17-1133036002.doc 1. Place a WF Graph onto the FP of a New VI 2. Make the Cursor Legend Visible (right-click on the Graph and choose Visible Items>>Cursor Legend) 3. Create a Cursor (right-click on the Cursor Legend and select Create Cursor>>Single Plot) 4. Undo the Create Cursor (choose Edit>>Undo from the menu or press <control>+Z) >>> Notice that the Cursor is not visible in the Cursor Legend but it is still present in the Graph. 5. Create another Cursor (right-click on the Cursor Legend and select Create Cursor>>Single Plot) 6. Click on the [-] Tree Node expander of the new Cursor. >>> Watch LabVIEW Crash CAR#: 3RRG36V2. Status: Fixed in 8.0.1

:headbang: Doh! It looks like the problem affects Multicolumn Listboxes and Tree Controls, too. The whole Drag and Drop, feature might be hosed in EXE's.

Neville: Eventually we will figure out a way to integrate into the LabVIEW 8.0 palettes. Until then, you can find the OpenG library palette menus beneath the OpenG subpalette. See here for more info.

Great idea! However, I just tried adding all of the settings in LabVIEW.ini to Listbox Test.ini and it did not help the problem.

Listbox drag & drop row reordering does not work in built executables. Run the attached example. Download File:post-17-1132853952.zip Notice that Listbox Test.vi works, but Listbox Test.exe does not. To prove that this is a problem with the Run-Time engine, change "Listbox Test.exe" to "Listbox Test.llb" and open "Listbox Test.llb\Listbox Test.vi" in the Development Environement -- the proplem goes away. CAR#: 3RK9A23A. Status: Fixed in 8.0.1

Norm: Long time no chat. Been working too hard ;-) I suppose that these keys have to do with the Simulation Toolkit features, which use a VI facade, similar to Express VIs (I think).

The Multiple Document Interface (MDI) is not available in LabVIEW 8.0, but might still make it into a future release.

Try this suggestion from NI Dev Zone:

Arlan: How about emptying the data from the cluster before getting the type descriptor. Here is a trick that you can use to get the default data of anything:

Yep, it's a bug.

Correct, you can only call one DLL at a time this way. Rolf's suggestion (to write the linker info to the VI and change the called DLL) was also on my mind but this method requires 1) That you be in the development environment, 2) have access to scripting, and 3) understand what linker info is. So, I avoided that solution. Actually, maybe there is another way to do it. I think that the link to the DLL path is stored in clear text, within the VI (binary) file. If you used a fixed width path like "My_Dynamic_DLL_NNN.dll" you could do a character replacement of the VI's binary information -- for example "My_Dynamic_DLL_001.dll", "My_Dynamic_DLL_002.dll", etc. This could allow you to open multiple instances of the DLL.