LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Code does not work as expected once is made as executable

Hi,

Somebody Can help me, I have a code (attached) that takes a screenshoot it works well in Labview but If I made it executable it does not work, I do not why

0 Kudos
Message 1 of 15
(3,961 Views)

Can you post a PNG file?  (Alt-Prt Screen and then Ctrl-V it into Paint, save as a PNG file)

 

I only have 8.2.1 here.

 

 

-Matt Bradley

************ kudos always appreciated, but only when deserved **************************




0 Kudos
Message 2 of 15
(3,959 Views)
How is the VI supposed to work? I don't see a loop (please don't tell me that you're using the continuous run button in the toolbar to run the VI), so I assume it's meant as a single-run app? What doesn't work? Do you get an error? A picture? No picture?
Message 3 of 15
(3,947 Views)

Does the error-out tell you anything?

 

(btw: your sequence structure has no purpose, delete it. Execution order is fully determined by dataflow alone.)

Message 4 of 15
(3,949 Views)

smercurio_fc wrote:
How is the VI supposed to work? I don't see a loop (please don't tell me that you're using the continuous run button in the toolbar to run the VI), so I assume it's meant as a single-run app? What doesn't work? Do you get an error? A picture? No picture?

It looks like it is probably called from within an event structure of a toplevel VI. Look at the connector pane.

Message 5 of 15
(3,943 Views)

Attached you will find the vi for 8.2.

0 Kudos
Message 6 of 15
(3,904 Views)

Yes, this is a single-run app. It suppose to take a printscreen when I run the application.

 

I run the vi in labview and it works good, it takes in an image the screen every time I run the vi.

I build an EXE but it doesn't work, it doesn't capture the image of the screen. There is not errors.

Download All
0 Kudos
Message 7 of 15
(3,895 Views)

You are using unsupported LabVIEW scripting to gain access to the Clipboard.GetImage method. These methods are not guaranteed to work, and National Instruments can't support you with this. There is no real way to determine if this will work in a built executable Smiley Sad

 

You might need to find another way to gain access to the clipboard data, such as Clipboard.Read, and convert the result into an image.

Thoric (CLA, CLED, CTD and LabVIEW Champion)


0 Kudos
Message 8 of 15
(3,879 Views)

Hi!

 

I'm actually very interested by what you are telling here. I'm developping a VI that create other VIs using the scripting. I've tried to build an .exe but it doesn't work whereas the .vi works perfectly.

Are you telling that the scripting isn't supported on .exe? Are you telling that a VI that uses the scripting Labview library can't be turned into a .exe?

 

Thank you.

Luc.

0 Kudos
Message 9 of 15
(3,503 Views)

Hi Luc.

I'm not an expert on scripting, but I believe the limitations are in the RunTime engine. The LabVIEW runtime is not a compiler, therefore executables cannot be used to create new VIs, this can only be done in the Development Enviroment.

Thoric (CLA, CLED, CTD and LabVIEW Champion)


0 Kudos
Message 10 of 15
(3,501 Views)