Why are pictures showing up in my VI, but not in the build .exe

[EngrStudent]

I have a vi that changes a picture based on control inputs.  It works in vi exactly as I like.

When I made it into an app, when I built it, the pictures do not display.

I'm not sure how to help you help me.  Can you point me in the right direction?

Is there a build-configuration that I need to show?

fwiw: I am using LabVIEW 2017 on Windows 7.

Thanks.

Engr Student.

[altenbach · Accepted solution]

How do you read in the pictures? Are they included as separate files? If you have an exe, some relative paths change and they might not be found. (details)

[EngrStudent]

Per the KB article I changed to "application directory" and it now works in the compiled version and not in the vi.

It is progress. 

Thank you, Altenbach.

[crossrulz]

---

@EngrStudent wrote:

Per the KB article I changed to "application directory" and it now works in the compiled version and not in the vi.

It is progress.

---

Move your image files to be relative to your project file and it will all be fine.

[Bob_Schor]

If you read the Help for Application Directory, you'll see that the paths are different (but logical) for a built Application and for the Development Environment.  For the Application, the Application Directory refers to the path to the folder containing the Application.  For the Development Environment, it refers to the path to the folder containing the LabVIEW Project File (.lvproj).

Bob Schor

[EngrStudent]

I wish there was a case that I could set up to determine whether this was the in-development vi or the built-application.  I could then put directories there. 

When I build, the directories are assembled per the build instructions. 

Even crazier, when I make an installer, the built directories are put in the program files (and such) per the installer setup. 

How do I test that, as an installed application, it acts like it should.  The US Army says "train like you should fight, because you will fight as you were trained".  I wish there were a non-hack, non-manual way to do that in the process of building standalone applications in LabVIEW.

[GerdW]

Hi Engr,

there's a property node telling you in which einvironment your VI is running.

You can even use a "conditional disable"-structure…

When I build, the directories are assembled per the build instructions. 

Even crazier, when I make an installer, the built directories are put in the program files (and such) per the installer setup. 

So everything is done as YOU have configured it!? What's "crazy" about that?

How do I test that, as an installed application, it acts like it should.

By doing some testing and debugging!? Error logging is a good idea, too.

[EngrStudent]

GerdW,

Can you show me a snippet??  This is neat.  I needed to know that.

-EngrStudent

[JensG69 · Accepted solution]

Here's the property node for that:

Regards, Jens

[EngrStudent]

Arms in the air, saying yes(!) out loud.

Thank you.