From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-03-2017 02:00 PM - edited 10-03-2017 02:30 PM
As mentioned several times, many users are too lazy to even give a proper name to a VI before attaching here (example).
This means that if somebody attached "untitled 1.vi" this morning, and somebody else attaches a set of "main1.vi" and "untitled 1.vi" VI in the afternoon, "main 1" will open with the old "untitled 1.vi" because the new version got renamed by the browser to "untitled 1 (1).vi" causing the caller to break or misbehave, and causing confusion for everybody trying to help.
Some related posts are here (Reply A, Reply B), but there are many more.
10-03-2017 02:43 PM
Hi Christian,
Thanks for the feedback. There isn't any functionality like this out-of-the-box. As a workaround, when encountering these types of filenames, you can right click > save as and rename it before saving the file locally.
Thanks,
Lili
10-03-2017 03:30 PM
Renaming will not work directly, because the caller expects a certain file name for the subVI (case # 2 above). If I have to first start herding cats before being able to look at the code, the chance of providing help is greatly reduced.
No big deal, though. Maybe the posting guidelines could add a few sentences about file naming. Personally, I prefer zip files whenever there is more than one file.