Strip Path VI error on exe version?

[Dennis_Knutson]

Vasilich2004,

The development environment is not the same as creating an exe with debugging turned on. If you have the latest version of LabVIEW you can in fact enable debugging and the Current VIs Path will return the exact same information as if you did not have debugging enabled. The function you seem to have a problem with is absolutely, 100% consistent. It alwasy returns the path to where the VI is. What you seem to have a hard time understanding is that the VI can and does reside in different locations. You could have the VI in a folder, llb, or in an exe. What you see as a bug is not.

[TCPlomp]

Hi 10Degree,

why don't you use the App.Dir property for applications?

Ton


Message Edited by TonP on 12-25-2007 07:50 PM

[tst]

---

@TonP wrote:

why don't you use the App.Dir property for applications?

---

I wouldn't use it because it would only work for applications. In the development environment it returns the path to the LabVIEW folder, which is usually not what you would want.

[Vasilich2004]

About what you talking guys?

Dennis Knutson

changes in version 8.5 (I didn't have chance to see that) confirmed the BUG by NI. I translate this changes to normal language specially for you, Dennis.

=======

Yes, there is bug in our naming. We (NI) mixed real OS path with our internal structure and path strip (and (an)other functions) work unclear. So programmers have headache. We try to decrease the trouble and did that ... But we don't like to do changes because ...

=======

How about that?

It is also funny to read - "as is well-documented in the various LV training materials that are available" from mikeporter. About which training are you? I don't have time for training and read help. Guys, help must point and explain that. Do you see that in strip path function?

If you use one language constantly it is not big problem. But if your projects use different languages than you have huge chance to forget small details ... Other couple excellent naming examples of LabVIEW are Structure and Cluster. Enjoy!

I think I explain the problem and why it is the bug. I wouldn't continue this topic.

Finally, Happy New Year!

[tbob]

---

Vasilich2004 wrote:

If you use one language constantly it is not big problem. But if your projects use different languages than you have huge chance to forget small details ... Other couple excellent naming examples of LabVIEW are Structure and Cluster. Enjoy!

I think I explain the problem and why it is the bug. I wouldn't continue this topic.

The real problem is that you have to use different languages and get mixed up with programming conventions between different languages, like cluster vs structure and file paths.  There is no problem with Labview and the strip path function does not have a bug.  It works exactly like it is documented to work.

I'm sorry that you are having this problem, but don't blame it on a Labview bug.  As a programmer using multiple languages, it is your responsibility to learn the differences in each language.  Sorry you don't have the opportunity to train well. but that really is your problem, not Labview nor NI's problem.  Best thing to do is to learn from this forum by listening to what the experts (like Dennis Knutson) have to say.  Please don't go knocking anyone here because you are having problems.

[tst]

---

@Vasilich2004 wrote:

changes in version 8.5 (I didn't have chance to see that) confirmed the BUG by NI. I translate this changes to normal language specially for you, Dennis.

=======

Yes, there is bug in our naming. We (NI) mixed real OS path with our internal structure and path strip (and (an)other functions) work unclear. So programmers have headache. We try to decrease the trouble and did that ... But we don't like to do changes because ...

=======

---

What are you talking about? What change?

I know that NI did change something in the internal file structure of an executable in 8.2.1 to allow the applications to be signed in Windows Vista, but I don't think this affects this behavior.

[10Degree]

astroboy,

No more 7.1 here - sorry!  Here is a picture.

-cb

[tst]

You should note that if the VI happen to be in an LLB this method will return the path to the LLB in the IDE and the path to the folder in the executable. That's why I said that it's better to strip until you know you got to the folder.

[Ben]

Vasilich wrote "...But if your projects use different languages than you have huge chance to forget small details ... "

And therein lies the elegence of tst's approach.

It will even claw its way up out of llb's dev or exe environments, cross-platform or whatever.

Ben

[mikeporter]

This question is pointless as there is nothing in C that relates to executing code in the LV development environment...

Mike...