FileSelectPopup not recognizing the default file spec parameter

[judyh]

Hi all,

I'm running into the same problem, but the DirSelectPopup does not save a file, only selects a directory.  I am allowing my user to save files in a pre-determined directory and prompt them with the file name based on some of its contents.  That file name was in the file selection box for them so they just had to click the save button.I need a fix for this.  Has it been released yet?

Thanks,

Judy Harrigan

[judyh]

PS.  I followed the link to the known bugs and found the following under that listing:

"However, there was also a behavioral change introduced in all versions of Windows Vista and later. For example, passing *.c as the defaultFileSpec will show files test.c, test.cws, and test.cfg. This is an issue with the underlying file dialog box and will not be fixed by LabWindows/CVI."

Is this true?

Judy Harrigan

[nickb]

Hello Judy -

Yes, this is true.  You can observe the behavior from a program like Notepad:

The service pack containing the fix for this issue will be available later this summer.  I'm sorry for the delay and the inconvenience.

NickB

National Instruments

[Randal L.]

I too am experiencing the FileSelectPopup failure to display the defaultFileSpec on the popup.

(we are using LWCVI 2010 on a mix of Win7, XP and older.)

There is an additional anomaly.  If you supply a defaultFileSpec, even though it does not display it,

it uses it to override the fileTypeList.

For example:  if defaultFileSpec is "presets.prst", and defaultFileSpec is "*.txt; *.sav; *.prst"

the popup will only display "*.prst"

this is also very inconvenient.

(when you say the fix will be out late summer, do you mean August, or October?)

[Steffen.Schmidt]

Nick, I haven't seen this bugfix in the release notes of CVI 2010 SP1...

Are you sure SP1 already contains it?

Thanks, Steffen

[nickb]

Hmm... You're correct, there appears to be a typo in the readme.  The bug that was resolved in CVI 2010 SP1 that should fix this issue is 279916.  You can see in the known issues list that it is fixed in 2010 SP1.  I will try to update the online CVI 2010 SP1 bug fix list soon.

Sorry for the inconvenience -

NickB

National Instruments

[JoeKenZ]

When was SP1 released?  I've ran NI Update Service just today and I told me there are no updates available as it has every other time I run it.  I would like to see this issue resolved soon.

[nickb]

CVI 2010 SP1 was released last week.  For some technical reasons, it will not show up in Update Service for about another month.  You can download 2010 SP1 from ni.com/downloads.  Be sure to select the "Current user" option. 

NickB

National Instruments

[nickb]

Also, I should point out that installing the CVI 2010 SP1 Run-Time Engine should resolve this issue.  The Run-Time engine is freely available for download here.

NickB

National Instruments

[JoeKenZ]

This peice of information came a little too late.  Now I'm stuck with an evaluation version of Lab Windows 2010 on my machine, instead of my fully functional  version of Lab Windows 2010.  Installing the runtime engine is an acceptable solution but now I understand I have to uninstall my NI software and reinstall my original version.  Is there an easy way that I can reinstall just CVI, or do I have to wipe out the hole developer suite and waste a day reinstalling.