09-11-2007 09:03 AM
09-11-2007 09:27 AM
hi there
we need code!
09-11-2007 09:40 AM
09-11-2007 09:56 AM
09-11-2007 11:51 AM
09-12-2007 06:32 AM - edited 09-12-2007 06:32 AM
Thanks Altenbach! This is what I suspect..
I am curious, with LV8.x (8.2 &up), is this still a problem when you use a project to build an executable?
The reason for asking is the link says it applies to LV8.2...
Primary Software: LabVIEW Development Systems>>Full Development System
Primary Software Version: 8.2
I had learned my lesson with this issue in LV7.0 / 7.1. Since then, I use a config file to store full path names and I stay away from "This path" or using relative path.
A nice learning exercise is to have an indicator show the relative path when using the source code and then building an executable and seeing the difference in path.. 😉
I did it in LV7.x. Maybe I should repeat the experiment. Nevertheless, if you look at the context help info, it warns you about using "Current Path" when building an executable.. See attached image.
Message Edited by JoeLabView on 09-12-2007 07:32 AM
09-12-2007 06:41 AM - edited 09-12-2007 06:41 AM
Hi zyl7,
If you look at you splash screen code, you're using the Current Path vi that I mentionned in my last post.
By the way.. very nice code. nice & clean, easy to read. I like it 🙂
I just noticed something after posting the image..
The error cluster wire after the Flat Sequence Structure is not wired to the property node.
Also check out "Presse.vi". Try not to hide the Queue reference wire (consumer loop) behind the Case Structure.
Message Edited by JoeLabView on 09-12-2007 07:46 AM
09-12-2007 09:49 AM