Re: [bug] get clipboard image fails in executable

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.

--------------------------------------------------------------------------------------------------------Kudos are always welcome if you got solution to some extent.

I need my difficulties because they are necessary to enjoy my success.--Ranjeet

Re: [bug] get clipboard image fails in executable

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).

Re: [bug] get clipboard image fails in executable

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.

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.

--------------------------------------------------------------------------------------------------------Kudos are always welcome if you got solution to some extent.

I need my difficulties because they are necessary to enjoy my success.--Ranjeet

Re: [bug] get clipboard image fails in executable

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.