Ulf

Which license type do you use in version 1.0.1? BSD or LGPL? The "Readme"-file states that version 1.0.0 use LGPL and this support page says that version 1.0.1 is under BSD.

I can't open or test your example as I'm using LabVIEW 11, but it might be some kind of virus scanning of your file, that affect the execution speed?

You have too much time(or quick tools) Mikael...

You can always put a help VI in the same folder as the class you want to load. The help VI should not be part of the class and should only return the class path. When you create your splash loader, you just drop the all help VIs that you have created and execute them one-by one to get the class-path.

Thats why I asked, I have never used AutoIT, so I don't know. Have you used it together with LabVIEW or other languages?

Does anyone have any recommendation of a tool that makes gui testing easier and automatic for LabVIEW? I have heard that some use AutoIT, is it any good?

I didn't think of that ;-) Measuring the launch time is probably a bad idea as you said. Seemed like a simple solution in the beginning though...

Can't really understand why this solution should be uniuqe for my private application? If the "splash screen" measures the time to load the main application and stores it every time, it will be quite accurate, even after driver/windows updates. The problem, which have been stated before, is to update the progress during loading.

In LabVIEW 2010 I collapse panes by moving the splitter bar to a "minimized" position. I save the splitter bar position before I collapse it, so that I can restore it to the position that it had before.

The load time is only unknown the first time you launch the application... if you store the load time you will display a proper progress bar the next time ;-)

Thank you...

The object reference is probably destroyed by the "automatic" garbage collector, when the VI that created the object "stopped" running. You have to make sure that the creator of the objects is alive and running during the whole execution. //Ulf

You have probably different application/dialog font and size in your OS. You can force a specific font and size to be loaded by the applicaition by adding the following lines in the INI-file. appFont = ""Arial" 15" dialogFont = ""Arial" 15"

You don't like restriction, do you? ;-) . I the short run that will be a "good" solution but in the long run, it will be quite messy if all "software developers" create their own folder from root level.

I have found some entries in regedit that I probably can use. Currently I'm only interested in two driver VISA and DAQ and I've to verify that the entries are created when the drivers are installed (for both 32 and 64 bit OS). - VISA: HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\NI-VISA - NI- DAQ: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\NI-DAQ\CurrentVersion (HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW Run-Time)

The problem with MAX API-functions is that you have to have MAX installed first... Catch 22 . The API was 155MB to install as well...

Thank you for the Reminder link. I missed that one

Hi all! I have an application that uses both VISA and DAQmx. I often email new releases of the application to the "customers" around the world. The built exe-file is around 10MB, so it can be emailed quite easially. The zipped file size with all installer included (LabVIEW runtime, VISA and DAQmx) is around 210MB. The additonal installer are only required at the first installation, so I don't want distribute them outside the office. The problem is that not all "new cutomers" read the instructions that they should download and install VISA and DAQmx(and, of course, LabVIEW runtime) manually from NI. Is there a way to look in the main code(from the "splash" starter) and look if anything is missing(in this case VISA or DAQmx) and then show a dialog or perhaps, try to download the missing driver. Another way is perhaps to look in the registry after DAQmx or VISA? How do you distibute your applications?

Thank you! Do you known if the installation program "uninstall" stuff in the ProgramData? I guess it quite easy to test... //Ulf

Hi All! When I build an application(and installation) I normally configure "application builde" to install the program under "\Program files\". I also place the ini-file in the same folder to make sure that correct settings are loaded when the application start. The problem starts if I want to write to the ini-file from the application, then the application have to run in admin-mode(you are not allowed to change anything in \program files if you not are an admin). The solution to this problem is to move the ini-file/config file to a different folder outside "program files" or use the registry. If I choose to move the file to a different folder, which one do you think I should use? At first I placed the file under "c:\users\user name\documents\application name" but then I realized that there where several other folders that I could use. What do you think the following folders are for? Should I use one theese folders instead of "c:\usesr\user name\documents"? c:\ProgramData\ (hidden) c:\Users\user name\AppData\Local Best regards Ulf

Yes, you are probably right.

Sometimes bluetooth is mapped as a comport as well.

What happen if you use two reentrent sub-vi and call them at same time? //Ulf

Hi, What happend if you call the reentrent VI as a normal Sub-VI, instead of using "Call by reference"? Does it work asyncronous then? //Ulf