LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

FileSelectPopup in LW/CVI not listing all directories/files in linux.

This is concerning a port of Windows based software to Linux.  The FileSelectPopup dialog does not list all the files and folders in the current directory.  For example, if I look in /home/pshrewsberry I can see everything but when look in /home I cannot see pshrewsberry!  Another example: If I am in a directory "test" which contains directories A,B,C and D only B and D are listed. The same happens with files as well: In the FileDialogTest directory that I have attached to this post when I browse this directory using FileSelectPopup I can't see the cvibuild.FileDialogTest directory (created after building) nor can I see the binary "FileDialogTest".

 

This problem does not happen in all directories that I browse through either.  I can't seem to find a rhyme or reason to it.  File permissions on all files in FileDialogTest (for example) are the same and UID and GID are same as well but the FileDialogTest binary and the cvibuild.FileDialogTest directory are not listed.  If I run as root I get the same results.

 

I have tested this in Linux with LW/CVI8 and the LW/CVI 2010 beta and I get the same erroneous results with both.

 

Could this be a bug in LW/CVI for linux?

Thanks

-pete

0 Kudos
Message 1 of 6
(3,976 Views)

I forgot to mention that I tried this in Ubuntu 10.04 and RHEL 5.2 both with same erroneous results.

0 Kudos
Message 2 of 6
(3,938 Views)

I will see if I can find a machine to reproduce this behavior

National Instruments
0 Kudos
Message 3 of 6
(3,910 Views)

Hello, we have reproduced this problem, it is certainly a bug. A Corrective Action Request has now been created for it and the number is CAR 248693.

Thank you for catching and reporting this issue!

National Instruments
0 Kudos
Message 4 of 6
(3,887 Views)

I'm not sure how to track a corrective action request.

 

What is the timeframe for this to make it into a beta or a distro.  I just went throught this before concerning another problem that I found.  We ultimately received an updated shared object file (*.so) to fix the issue before the ultimate release of fix in beta.  That resolution is preferable for this issue as opposed to waiting for the next official update.

 

Thanks,

-pete

0 Kudos
Message 5 of 6
(3,829 Views)

Hello Pete, it is too soon to tell how R&D will allocate resources for the next release. Any CAR fixes that make it into the next release will be documented in the relase notes for that version, so that is the best place to check in tracking this CAR. We are of course continually trying to improve our product and prioritize the most impactful bug fixes. I am sorry that I do not have any more information at this time.

 

Thanks,

National Instruments
0 Kudos
Message 6 of 6
(3,801 Views)