Michael Aivaliotis

I have a pet peeve of LabVIEW 7.1. I have a strict-typed enum constant inside of an array constant on the block diagram. Sometimes I resize the width of the enum to see the full text. When I update the strict-type of the enum with new values, the width of the enum reverts back to some standard width. I cannot figure out what LV uses as the default width and where this comes from. It doesn't appear to use the smallest text width or the largest. I wish LV kept the width as I had originally set it. If no-one has any solutions, I'll move this post to the wish list...

This is the holiday cheer thread. Feel free to add a reply of greetings for all members. I spent the first holidays in my new home. It was strange. Christmas eve was warm, not a cloud in the sky and the temperature was warm: 20 celsius. It's really not Christmas unless you have snow on the ground...

Some of you may be using this type of lock for your system: Watch a video that shows you how to break into it.. http://www.toool.nl/kensington623.wmv Makes you think twice about trusting these things eh?

Yes, but it's now available as a function:

This post is a prime example of how NOT to ask for help from the forums... However, if you're willing to buy me a new car then I will consider helping...

Bottom-lin: You cannot change the color of any Dialog (system) controls. If you need to change the colors use non-dialog controls.

So how is this book related to LabVIEW? Oh, I guess it's not...

Just a reminder that the deadline for the submission to the challenge is close approaching. There are only 2 weeks left!

This was reported by George Gatling on Info-LV: 1. Drop combo box on front panel. 2. Drop string indicator on front panel. 3. Wire them together. 4. Enter a couple of items into the combo box. 5. Right click the combo box and deselect "Allow undefined strings" 6. Try to enter an undefined string... doesnt work... yay! 7. Start typing one of your items, but stop somewhere in the middle. 8. Hit backspace.... uh oh... 9. Run the VI and look in the string indicator. 10. Looks like an undefined string to me! Boooo!!! Reproducable?

Have you seen the "point-by-point" analysis? This will do what you want but you need to change your output accordingly. The Acquisition and Analysis probably needs to happen in a closed loop.

This seems to be a bug. The scale to fit was added in 7.1 I believe. It didn't exist in prior versions. You can still scale to fit by using the X,Y scale to fit buttons as shown in the attached image. Another alternative is to create your own button and use property nodes to toggle the XY scale buttons circled in the image. BTW, this is fixed in LV8.0 :thumbup:

It takes about 15min. on my machine. Also, you can add the following bit of code to display the pre-made hierarchy faster. This will avoid having to wait for the list to populate:

Have you looked at the code? Do you need everything spelled out for you?

One way to simplify your code would be to use the reshape array function. See attached image. You still need to check if the index goes beyond the original array size but this method is more efficient.

This is not a problem specific to LV8. This is a general problem that has been there for many revisions. You have grouped two front panel controls and decided to scale them. You can't do this. You can only enable scaling on a single front panel control. Ungroup the controls and enable scaling on the large top text box. You will see that the scaling works properly without drifting. Here is another thread on some more front panel scaling tips: http://forums.lavausergroup.org/index.php?showtopic=1717

Well, I would suggest using an event structure to capture the arrow down keypress. Use the event on the VI panel called Key Repeat. From this you capture when the arrow is pressed and held down.

Ya, LabVIEW only instanciates the caption if you actually show it at least once. Perhaps this is to reduce unnecessary memory usage.

I would say most of them are NI toolkits... Except for the OpenG.

Ah, well you need to create a custom pop-up VI. Put a timer inside of it and have it close after a certain timeout.

If you don't know what the datatype is at design time then you have a significant challenge ahead of you. I've done exactly what you describe using variants for a flexible test system I built, however I used the OpenG variant tools. The OpenG variant tools are really cool! :thumbup: You can do everything you describe. They were created by the one and only jpdrolet . The best part... you don't have to write a single line of code.

Have you tried notifiers or queues? What is your opinion on that?

Just place a sub-vi on the diagram. Then go to the sub-VI's properties and set: Open panel when called, AND close afterwards if originaly closed.

There is no need to rename the file. Just open it in Excel. Have you tried this? Thanks for the link...

Well it looks like NI cleaned up the code a little bit on the 3 button dialog box in LV80. The previous version used a stacked sequence structure. The current version uses a flat sequence structure. Which one is better? I'll let you decide. In my opinion... niether. Hasn't NI learned about the state machine? It's required reading if you want to pass the NI certification. Hmm, I wonder how many NI LabVIEW developers are "Certified".

I don't know why but all this buying (and litigation) on NI's part is disturbing me... A can't put my finger on it. It's like playing the game Civilization. For a while, you try to get along by forming coalitions and becoming a good citizen hoping nobody notices you. After a while, when you have enough gold, you build a huge army and start blowing everyone away.