NI: Please don't put illegal vi names in your toolkits, thanks

[billings11]

Http Standalone?.vi

Not An FTP Session?.vi

DoNIsEngineersKnowThatQuestionMarksInVINamesAreConsideredIllegalByTheABAPIAndWillBreakAppBuilds?.vi

These vi names with question marks will break a build.  The ones I found were all part of the internet toolkit.  Please don't do this anymore NI.

[MikeS81]

Hi billings11,

in which palette did you find these vi´s?

Mike

[waldemar.hersacher]

Hello Mike,

Not An FTP Session?.vi is located in <vi.lib>\addons\internet\ftp\ftp0.llb. Others will be in other LLBs of the internet toolkit.

I think this is a bug of the application builder since ? are allowed characters in LLBs. The problem is that ? is not allowed in the Windows filesystem as part of a filename. The VIs in a LLB should avoid any character which are not allowed in any of the supported OSes.

[MikeS81]

Thanks Waldemar,

now i found them.

Mike

Message Edited by MikeS81 on 07-17-2008 08:55 AM

[Mythilt]

Yeah, the Open/Create/Replace File.vi in the File pallette has had that problem for years, I have to manually go in and modify any HTML VI documentation that we generate for our projects when the VI being 'printed' has that as a subVI.

[NI-Bob]

Hello billings11,

Thank you for contacting National Instruments.  I do apologize for the frustration that the file names are causing.  My best recommendation to you at this point would be to create a product suggestion.  We take all product suggestions very seriously and a lot of them help shape new functionality when it comes to creating new versions of LabVIEW.  To create a product suggestion, please go to The Product Center.  You will need to sign into your account and then you will be able to submit a new product suggestion for this issue.  Again I do apologize for the inconvenience of the unintended effects of the file names but with this product suggestion we will hopefully be able to change it for future versions.  Thank you for your patience and understanding.

[Travis_M.]

Hello Billings, I'm actually going to look into creating bug reports for these instances.  I'll also be sure to stress that it is important that we add mutation code and/or compatibility VIs to help those who are upgrading if these VIs get changed.  Thanks for bringing this problem to our attention.

[billings11]

Bob,

I don't have time to fill out a special product suggestion.  This is not a product suggestion anyway; this is a bug report.  I have reported the bug on this forum.  You have seen it, and you work for NI.  You fill out the bug report.  My job is done, now it's NI's job to fix it.

Thanks.

[NI-Bob]

Billings11, thanks for bringing this issue to our attention, my apologies for misunderstanding the original post.  Travis and I went ahead and created a couple of bug reports on this issue (#120518, and 120633) to fix the internet toolkit VI names, as well as to look into a system to prevent occurrences like this from occurring again.  Thanks again for reporting this to us.

Jon D, I am interested looking into your situation in more detail.  Those file primitives (and others like "Search/Split String", "Get Date/Time String", etc...) shouldn't be actual files anywhere on the system (unless you are using the compatibility VI in the "_oldvers" llb which no longer does anything but return an error).  Could you elaborate a little bit on the problem you experience with files of these names, and perhaps attach an example?

[Mythilt]

---

Bob_H. wrote:
Billings11, thanks for bringing this issue to our attention, my apologies for misunderstanding the original post.  Travis and I went ahead and created a couple of bug reports on this issue (#120518, and 120633) to fix the internet toolkit VI names, as well as to look into a system to prevent occurrences like this from occurring again.  Thanks again for reporting this to us.

Jon D, I am interested looking into your situation in more detail.  Those file primitives (and others like "Search/Split String", "Get Date/Time String", etc...) shouldn't be actual files anywhere on the system (unless you are using the compatibility VI in the "_oldvers" llb which no longer does anything but return an error).  Could you elaborate a little bit on the problem you experience with files of these names, and perhaps attach an example?

---

The problem was when I was printing the documentation for the VI as an HTML file.  As part of the documentation, I would add the list of subVI's (Print->Print Contents->VI Documentation->List of SubVIs and Express VIs selected).  When the HTML files were generated, if you looked at the HTML, where the Open/Create/Replace.vi would be listed in the subVI's list, would be a broken link, because no Open/Create/Replace.png coulld be created.

I do note that when I tried to replicate this with 8.5, that the Open/Create/Replace.vi doesn't cause a problem because it appears that primitives aren't added to the list of subVI's anymore with that print option.