Invalid characters in paths

[reischlb]

Hi All,

i think it would be useful to have one VI which can check path constants whether they contains invalid characters or not. 

A lot of VIs doing some file operations returns errors if the file contains invalid characters but it should be checked before calling the VI with the file operations.

I found the `Is Name Multiplatform VI` which can check it, but it is hard to find that this VI will solve this question, accepts strings as input instead of paths, and also it has a lot of unnecessary in and outputs.

I think it would be would be more useful if there would be a simple VI with just one path input and one boolean output to check the path against the current platform.

What do you think about it?

[wiebe@CARYA]

That would be a nice to have. I've used this .NET function in the past. Of course it won't be platform independent until .net is supported on Linux and Max (if ever). And the list of illegal characters is well documented. This function probably validates the entire path, not just the characters.

[crossrulz]

Turning the Is Name Multiplatform.vi into a polymorphic or malleable VI would be one solution.  If it isn't in NXG currently, perhaps a name change there would be worth considering.  I doubt we will see the name change for LabVIEW 20XX.

[AristosQueue (NI)]

I flagged this conversation for the LV NXG team. They agreed that it is a reasonable request and added it to their backlog to consider for future revisions.

I'll leave the idea open for LV 20xx.