Michael Aivaliotis

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.

Have you browsed the VI's in the LV palette? You never know what you might find. Perhaps this is not the complete solution but hey...

It works fine for me in 7.1. The Tmp_Called.vi unloads itself properly. There were some bugs in 7.0 that were fixed in 7.1. Also, try using the older method of closing the panel. I've attached an image that shows the Front Panel Open Property set to False. You also don't need the Abort VI method. Remove this. As a general comment, I'm struggling to figure out why you are jumping through these hoops. There are simpler methods to acomplish your goal. Have you investigated queues or notifiers? These open a named reference that is easier to manage.

I know that OpenG builder allows you to import an NI build file. This means there is code out there to read this info. Why not download the OpenG builder and poke around? Of course, the real question is, "why do you need this?" Perhaps if you let us know, we might find another solution to your problem.

If your text file is a tab delimited file with new rows seperated by carriage return and linefeed, then you can simply open it from Excel. Excel should recognize the format and load it up without problems. The other option is to do activex com to Excel and pump the data directly into Excel. This option may take several days or weeks to get working (if you've never done this type of thing before). This method is cool, you will grow as a programmer and you can impress others with the new knowledge you have attained. Of course your boss might yell at you for pushing out the deadline on delivery...

Yes, it appears to make it through intact. Interesting however, LV doesn't color it light blue. This would lead me to believe that there is a mask in place. Well, I know PJM_LabVIEW has built a tool here that pulls everything out. Let me try that... Ho hum... Oops, LV8 throws an insane object error!! :ninja:

Hey, I was browsing around to see what new scripting stuff is in LV8.0 (the old ini keys seem to work) :thumbup: . I couldn't find the diagram reference property. Has it been moved... or removed? Also, I noticed a nice feature. All the private methods and properties are now light blue in color. This will be nice for quick recognition of scripting stuff in your code.

I've updated all the links to Jim's new posted location. It should work now. BTW, I used Firefox default download system and it worked the first time, perfectly. :thumbup:

I guess we made the classic blunder of debugging 101: is it plugged in? Of course GPIB will not work without VISA. I guess you take certain things for granted after a few years. CVI includes all support modules? Even the entire VISA install? I haven't built an executable with CVI, if you have, then you probably know better. There is one simple workaround... don't use VISA. Use the basic GPIB functions. I've been using them on and off for over 10 years now without any headaches. Of course there are good use cases and arguments for using VISA. However, none of those arguments justify their usage in the applications I have written.

The important thing to note: The front panel of Tmp_Called.vi MUST be opened before it can register for events. So the panel must be opened and then the Vi must be run. Also why not send a TRUE event to BooEve? How can you tell if it's working if you are sending a FALSE?

Hmm, If you look into you 6.1 Installation CD, you will see a folder called LVAppBuilder. Have you tried running the LVAppBuilder.msi that's inside that folder? I can't see why you would get this issue if you just run that installer. Another option is to run the installer on another machine and then copy the App Builder files into the machine that needs the app builder. I don't think registry keys are necessary for App builder to run.

Since when? This is not true. NI's web server supports Mozilla browsers as well. Where did you get that information from?

It worked fine for me on the first try. I guess you already primed it for me huh? :thumbup: I guess the drivers portion is not included with the download eh? It prompted me for it. BUT, this time, the installer doesn't abort the installation if the driver CD is missing. Unlike 7.1 which uninstalled everything if you didn't have the driver CD.