Hi, Does WINE support access to clipboard data across WINE processes. For e.g. one app opens the clipboard and sets data into it using SetClipboardData, closes it and then exits. The other app tries to retrieve this data. It works in windows but doesnt seem to do so in WINE. Regards Santosh Siddheshwar ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************
The short answer is no. We did have this functionality before and much of the code is still in cvs but it was broken for some time and I've disabled it. With a little bit of work it could be added back.
There are other ways to do this such as using klipper.
/Ulrich
On Wed, May 12, 2004 at 06:00:35PM +0530, Santosh Siddheshwar wrote:
Hi, Does WINE support access to clipboard data across WINE processes. For e.g. one app opens the clipboard and sets data into it using SetClipboardData, closes it and then exits. The other app tries to retrieve this data. It works in windows but doesnt seem to do so in WINE. Regards Santosh Siddheshwar
Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind.
This would be a deficiency (or so some say) of the X clipboard design. There is no "storage buffer" for clipboard data.
A process, when it hits Copy (SetClipboardData) registers that it owns the clipboard. When another program hits paste, only then is the data transfered between the processes. It is this way to support content negotiation... where the data that gets copied or pasted might be a different format depending on where you paste it. Plain text, HTML, RTF, etc.
A downside is when the owning program closes, the data is lost.