.txt file can't read after creation of executable

[Jim_Kring]

---

@altenbach wrote:

Ah, yes. OpenG seems to have implemented something similar.

I really should install these libraries one of these days. 😉

---

Yes, you should, Christian.  It's easy -- here's a short video that shows how to install them. 🙂

[tbd]

Hi jofe,

      This VI will give you the right parent-directory (whether VI, EXE or LLB), it also strips off the caller's name-prefix -  which is useful for building file-names ("ini", "dat", "log", etc) that have same name as the caller.  For those rare cases where you need to build a path to a neighboring VI, it also returns the immediate parent-path (which may be an EXE or LLB name.)  I use a VI like this in the top-level VI of practically every project!

http://forums.ni.com/attachments/ni/170/151993/2/Util.VI.ParentDirectory.vi

Cheers!

[altenbach]

---

Jim Kring wrote:

Yes, you should, Christian.  It's easy -- here's a short video that shows how to install them. 🙂

---

Hi Jim,

Yes, I know! You guys really wrote an absolutely fantastic interface and set of tools. :):D

My LabVIEW use is probably a bit different than most. I had the openG commander stuff installed a few years ago, and never really used any of it. Then there's the issue of "Palette bloat", which I abhor with passion.

I have much less than a dozen custom VIs in the user palette and that's all I really ever need for my work.

Just recently I installed the newest VIPM and installed one of the libraries to test the performance of one of the VIs  discussed here a while ago. I ended up corrupting the openg installation within 10 minutes because I did some editing and then pressed "save all" by accident on a different open VI (slip of the mouse), overwriting the openg tool with a broken version :(.  At the moment, I have VIPM installed, but none of the sets activated. 😉