Problem with FileSelectPopup

[roslocke]

We have a long term problem with the FileSelectPopup dialog. It seems to be computer dependant, so it might be something to do with the Exporer settings, but I've been unable to figure out what.

The problem is that when the "File of type:" field is set to the required type, e.g. "*.bmp" or "*.*", no files are displayed. However, when "*.bmp" is typed into the "File name:" field then they all appear, (see attachment).

Alternatively if one navigates to top level, (C:\), then sets the "File of type:" field and then navigates back to the required folder all the filenames can be seen correctly, until the field is changed, upon which they all disappear again.

This behaviour makes it very frustrating and confusing to use.
We first had this problem with cvi version 6.0, now we use v7.1.1 under XP SP2.

[blakney]

I have noticed a similar or maybe the same issue(s) with FileSelectPopup. I first really noticed this in WinXP OS. there are two scenarios that bring out the blank screen issue for me. I am now using CVI 8.1 but definitely had same problem on 8.0, 8.0.1 and I think 7.

First when the user switches file type, all files in the popup go away. Assume that given the below FileSelectPopup call and that the user deselects *.exp and chooses *.dat instead. The file dialog box will go blank. You must leave the directory and return and they reappear.

Second, the drives never appear in the dialog  if you select "MyComputer" from either the pulldown or the big button to the side. You must instead use the pulldown menu to select / switch drives.

In case construction is an issue,  here is a call that causes issues for me.

status = FileSelectPopup ("", "*.exp", "*.exp;*.dat;*.txt",   "Open Experiment", VAL_LOAD_BUTTON, 0, 0, 1,  0, file_name);

[Jon_M]

blakney,

I did not reproduce either behavior on my computer. Does this occur on more than one computer on your end? If so it could potentially be a setting in Explorer that we can change.

Message Edited by Jon M on 05-07-2007 10:39 AM

[blakney]

I finally found it. If you set a very large Maximum Stack Size (700MB in this case for a huge table) under Options>>Build Options you should see the behavior.

I don't think it is a total memory problem as this occurs on a 4GB laptop as well.

I am 99% sure this is causing the problem, please confirm.

Sorry my iteration time here was limited to the availability of Grad students with Vista and my family vacation.

Greg

[blakney]

Oops wrong older thread although likely related thread.