FileSelectPopup loading very slowly and displaying too many filetypes.

[PaulGanssle]

So this is something I've noticed recently on two Windows 7 Machines - when using FileSelectPopup, the first time I call for a FileSelectPopup, there's a good 2-3 second delay before the window pops up. Subsequent calls are much faster, but still on the order of 700ms-1s. Is there a way for me to reduce this time? I'd even be happy if I could make it so that the first call to FileSelectPopup were a bit faster. I'm guessing that since there's a change in the delay, that the first time it's called loads some kind of module that takes a bit to load - can I preload this module during startup?

The other problem I'm having with FileSelectPopup is that if I call it with the filetypes parameter set to "*.tdms", it will show me files with the extension .tdms, but also with the extension .tdms_index. This is quite annoying, as every single tdms file generates a tdms_index file as well, so it cuts in half the number of files I can display in a single panel. Is there a way to enforce that the ending is EXACTLY .tmds?

[D_Biel]

Paul,

Both of these are known issues and relate to the underlying file dialog in Windows Vista and Windows 7. The delay in the first call to the dialog is an issue that comes up time to time and seems to be related to Windows and is specific to the system. Do you experience this same delay in other applications?

As for the extension specifier issue, this is included in the Known Issues List for CVI 2010 and 2010 SP1 (as well as prior versions).

[PaulGanssle]

I haven't noticed the delay in any other application on either of the two Windows7 computers I used it on, but LabWindows exhibits the behavior on both machines.

It's disappointing that the defaultFileSpec issue has no known workaround and will not be fixed by LabWindows.

[D_Biel · Accepted solution]

Paul,

I may have told you information that is not completely correct. So let me correct myself. The issue that you have described actually known issue 247402 that was fixed  in CVI 2010. You can read about it in the CVI 2009 Known Issues List. The issue I linked previously is actually a separate, but similar, issue and the description may have been a bit misleading. I am going to correct this wording, but keep in mind that this was actually fixed in 2010 SP1. I would recommend using CVI 2010 SP1 Run-Time Engine in order to have the fix for both bugs.

[PaulGanssle]

Oh, cool, upgraded the runtime engine and it fixed the issue with the .tdms_index. The slow loading still persists after the upgrade to the 2010 Runtime engine, but I guess that's not so bad.