From 11:00 PM CDT Friday, May 10 – 02:30 PM CDT Saturday, May 11 (04:00 AM UTC – 07:30 PM UTC), ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
When searching for a single pattern we define the pattern as *.vi (for example). If we want to filter out say three patterns like (*.c, .h,*.txt). It doesnt work that way. In file dialog if we define these patterns seperated by semicolon it returns the desired result but in list folder we have to use a for loop for multiple pattern searches. Will it not be useful if we define (*c;*.h;*.txt) in the pattern and get only these files?
Just to be sure I'm on the same page: you know this is currently possible, but would just prefer a cleaner, documented syntax? Is that the gist of this Idea?
I believe that Muks is referring to the 'List Folder' Function where you can only specify a Windows-type wildcard (* or ?). My guess is that this function relies on an underlying OS call, and adding this functionality will require a different implementation.
I really like this idea. I also just got burned because on RT targets (like Linux), the pattern is case sensitive so if I have the following files in my folder test1.png, test2.Png, and test3.PNG passing *.png will only return test1.png. It would be nice for the pattern to be case insensitive to avoid requiring all permutations of capitalization to the array of file types to look for.
I just wasted an hour until I realized that providing a pattern of "*.tif;*.tiff" to List Folder returned ZERO files, while using only "*.tif" did return plenty.
This silent killer is pernicious as it returns no error when provided a multi-file pattern!
Multiple patterns in "List Folder" function is a nice idea and I fully support it. Of course, workarounds do exist, but for the shake of completeness and compatibility with the "List Folder" dialog menu, it should be implemented in the Labview core.