09-11-2013 04:17 AM
What wrong with my question RavensFan, I know how clipboard works. I just want to ask if he is using LV to store image to clipboard and read back then instead of writing image convert it into array and write and read back.
09-11-2013 04:42 AM
Hi Ton,
Thank you for letting us know about this bug. It is actually already entered in our system for correction.
The recommanded workaround is the .NET code that Colin has posted.
It should work properly for you. The Clipboard class is a static class so no need for a constructor (which is why you have a null reference). Just place a .NET Invoke Node and select the "System.Windows.Forms.Clipboard" class.
To have it working, you need also to use the User Interface as Preferred Execution System (FIle>>VI Properties>>Execution).
Kind regards,
09-11-2013 08:51 AM
@Ranjeet_Singh wrote:
What wrong with my question @RavensFan, I know how clipboard works. I just want to ask if he is using LV to store image to clipboard and read back then instead of writing image convert it into array and write and read back.
I'm glad you understand how the clipboard works. But you are making statements and adding things to the conversation that Ton never said he was trying to do.
Where did he say he was "using LV to store image to the clipboard."? He didn't. He is trying to GET the image from the clipboard into LabVIEW. He never said where the images on the clipboard were coming from.
09-12-2013 09:08 PM
Hello Cédric,
do yo know a CAR?
And yes changing the execution system fixes works around this issue.
Ton
09-12-2013 09:57 PM - edited 09-12-2013 09:58 PM
@RavensFan wrote:
I'm glad you understand how the clipboard works. But you are making statements and adding things to the conversation that Ton never said he was trying to do.Where did he say he was "using LV to store image to the clipboard."? He didn't. He is trying to GET the image from the clipboard into LabVIEW. He never said where the images on the clipboard were coming from.
That is what I also told him in my previous replies, Instead of image, convert it into array and store the array and read same but when presenting to user convert it into image.
09-12-2013 10:05 PM
09-13-2013 01:10 AM
Hi Ton,
Yes, the CAR#422317 is filed for it.
Kind regards,
09-13-2013 02:49 AM
@tst wrote:
@TCPlomp wrote:
My current workaround is using greenshots with a fixed config that stores the print-screen action in a pre-defined place.
You could probably also use the VIs Rolf linked to in the LAVA thread. As far as I know, they should work (although they probably need to be tested on newer versions of Windows to make sure).
They would need to be revised and upgraded to work for 64 bit LabVIEW. That would mean LabVIEW 2009 and newer only though as there was no way to configure Call Library Node pointers in a way that they behave in either LabVIEW bitness correctly before that.
12-31-2013 12:01 AM
Hi all the repliers,
I find another solution that get the clipboard image. Hope it is helpful for next follower.
Use the IMAQ ClipboardToImage.vi under vision module, it can get the image successfully, but not verify it after build executable file.
Home--colinzhang.net: My Blog
01-13-2014 06:50 AM
Hi,
I had the same problem. Solution of cedhoc works! .NET Invoke Node Get Image work correctly also as executable.
Thanks for the help!
Simyfren