Bug 61876 - [Clipboard] API to _add_ content to the clipboard
Summary: [Clipboard] API to _add_ content to the clipboard
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Kevin Barnes CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-12 06:31 EDT by Martin Aeschlimann CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2004-05-12 06:31:46 EDT
20040512

In the Java editor we add extra information to the clipboard on copy and paste.
But (as far as I know) the only way to manipulate the clipboard is set (replace) it.
I currently solve this by making assumptions that the styled text widget only
uses the text and the rtf transfer, so I read them and enhance them with my
information.

Is there a way to get all the current tranfers, or is there a way to 'add'
instead of 'set' the clipboard?
Comment 1 Veronika Irvine CLA 2004-05-12 15:56:17 EDT
Clipboard.getAvailableTypes() returns a TransferData[] which will give you all 
of the currently available types.  Note that some of these types may not be 
supported by SWT (e.g. image data transfer).

New API for "adding" to the clipboard will not be created in 3.0.  Currently, 
we do not use a lazy mechanism for presenting the data to the OS clipboard.  
Therefore this change would require a complete rework of the Clipboard on all 
platforms.
Comment 2 Dani Megert CLA 2004-07-29 09:05:25 EDT
>Clipboard.getAvailableTypes() 
We know about this one, but how can this be used to get the data using
Clipboard.getContents(...) which expects a Transfer and not a TransferData object?
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:22 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.