| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The pattern we generally follow is to put the
async result right after the source object, in
finish functions. Do this for gdk_clipboard_read_finish.
|
|
|
|
|
| |
Clipboard managers will be so happy once the backends actually implement
it!
|
|
|
|
|
|
|
|
| |
Also make clipboard_claim() a vfunc so backends can override it.
Because the whole operation a vfunc, backends have the option of adding
code before the actual claim is done and potentially even fail or do
something after the successful claim.
|
|
|
|
|
|
|
| |
This requires implementing a "pipe" so we can have 2 streams running:
contentprovider => serializer => outputstream
inputstream => deserializer => reader
And the pipe shoves the data from the outputstream into the inputstream.
|
|
|
|
|
|
|
|
| |
This allows us not just to pass any mime type to the read function, but
it also makes it possible to pass multiple mime types and the clipboard
can then try them in order until it finds a supported one.
This is so far not implemented though.
|
| |
|
|
|
|
|
| |
This allows the remote clipboard to take over. The X11 clipboard already
does that.
|
|
This commit adds a GdkClipboard object which is intended to
replace GtkClipboard, eventually.
|