LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"File Dialog" Express VI returns the wrong path when the user selects the desktop

In labview 8.0.1 with Windows XP, the File Dialog Express VI seems to return something other than the path selected by the user when configured to browse for folders (or files and folders) and the user selects the desktop.

I can't determine exactly when it works and when it fails, but it always seems to fail if the user selects the desktop from the places bar (the shortcuts on the left side of the dialog) or from the drop-down menu at the top of the dialog and then clicks the "Current Folder" button to dismiss the dialog.  In this case it always returns whatever path is wired to the "Start Path" terminal.

If the user navigates to the desktop with the "Up One Level" button or by selecting the actual desktop directory under Documents and Settings, the correct path is returned.

If the user selects a file before clicking the desktop icon, then clicks "Current Folder" the correct path is returned.

If the user clicks the desktop icon, clicks open, then clicks "Current Folder" the correct path is returned.

It's possible to work around this bug in most cases by setting the start path to the desktop.

Has anyone seen this behavior before?

Can anybody verify this behavior by running the attached VI?

In the past, when I've reported issues like this I've received responses from NI engineers that basically said "Thanks, but we already knew that".  Is there anywhere that users can search the list of known bugs and avoid wasting time tracking down issues that are already understood by NI?

Thanks,
Adam Brewster


0 Kudos
Message 1 of 3
(2,872 Views)
I'm on 8.2 and I can't get it to fail no matter how I select the desktop. I haven't tried it in 8.0, but I imagine that if this really is a bug, they did know about it and fixed it with 8.2. If this causes a real problem for you, I would suggest upgrading if you can.
0 Kudos
Message 2 of 3
(2,871 Views)
I guess I should have just tried on 8.0.1. It works fine for me there, too. I'm not really sure what could be causing this on your computer. Maybe someone else will be able to chime in that sees the same problem.
0 Kudos
Message 3 of 3
(2,864 Views)