LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

application builder vi does nothing

I have a lvproj that I am trying to build an installer for.  In fact, I built the installer, and it seems to install fine on several machines, however the actual VI does nothing at the moment.  I have attached the folder containing all of the subvis and the project (R&D Tools is the main vi).  I am very new to application building (this is my second), and am not sure where to look next.

 

The first one I built deployed fine.

 

Keep in mind that this application is not entirely finished, but I did want the functions I have completed to run on another machine (I also have everything spread out way more than necesary, but it should be readable).  Additionally, there are a few things that are still a little bit clumsy in the VI (Mainly the color scheme load from an xml file), but I was primarily exploring with that function, and it is on my cleanup list. 

 

Just thinking "out loud" but is might my color configuration be keeping the vi from executing, as it can not find the file?  I included the file in my build, but the VI contains a direct reference.  Is there a better way to do this?

 

0 Kudos
Message 1 of 21
(3,142 Views)

I didn't see anything inherantly evil in the code.  Could be cleaner and the initial case structure seams odd but I don't have the software spec you are working too.  Replace the path constant with a this vi's path and strip and build a path relative to the top level vi.  Thats the easy way 


"Should be" isn't "Is" -Jay
Message 2 of 21
(3,136 Views)

Well I definitely feel a little less than smart right at the moment.  Pretty clearly that file reference is what is screwing me (wired a false to my case for torubleshooting).  Snipet posted below. 

 

What is the proper way to store data such as this?  It is just the tab colors, and I could eliminate that function easily, but I am sure I will have reasons to store this type of data again in the future, and will need them to store data specific to the user, on the users machine.

 

 

 

 

0 Kudos
Message 3 of 21
(3,135 Views)

Jeff,


That makes sense to me.  Just wasn't sure if there was a better way.

0 Kudos
Message 4 of 21
(3,132 Views)
0 Kudos
Message 5 of 21
(3,115 Views)

OK,

 

So I have implented smercurio's suggestion, and it works great on the PC I have labview installed on.  When I run the installer on any other computer however, the VI still does not execute.  It acts as if the event structure is not queueing the state machine.  I've tried juggling a bunch of stuff around to solve this, but to no avail.  If someone could take a look at my build settings, maybe I am just missing something?

 

Like I said, it installs fine, and opens, and I can click through the tabs, but not even the stop button works.  I've attached my most recent rev.

0 Kudos
Message 6 of 21
(3,093 Views)

At a huge risk to my personal computer!  I'll extend an offer only once.  attach the installer....it should be working? Optionally (and preferable) have you tried remote debugging the exe?.  a fast search will show the needed steps to remote into the target exe from the PC with the IDE on it


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 21
(3,086 Views)

I will try the remote de-bugging first.  Perhaps I can locate the issue that way.

0 Kudos
Message 8 of 21
(3,080 Views)

@krwlz101 wrote:

I will try the remote de-bugging first.  Perhaps I can locate the issue that way.


I almost garuntee it!  good hunting!


"Should be" isn't "Is" -Jay
0 Kudos
Message 9 of 21
(3,074 Views)

@krwlz101 wrote:

I will try the remote de-bugging first.  Perhaps I can locate the issue that way.


I almost garuntee it!  good hunting!

 

YEAH Double posts--- good for the count


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 21
(3,073 Views)