Clipboard
Object Hierarchy:
Description:
The Clipboard object represents a clipboard of data shared between different processes or between different widgets in the same process.
Each clipboard is identified by a name encoded as a Atom. (Conversion to and from strings can be done with intern and name.) The default clipboard corresponds to the “CLIPBOARD” atom; another commonly used clipboard is the “PRIMARY” clipboard, which, in X, traditionally contains the currently selected text.
To support having a number of different formats on the clipboard at the same time, the clipboard mechanism allows providing callbacks instead of the actual data. When you set the contents of the clipboard, you can either supply the data directly (via functions like set_text), or you can supply a callback to be called at a later time when the data is needed (via set_with_data or set_with_owner.) Providing a callback also avoids having to make copies of the data when it is not needed.
set_with_data and
set_with_owner are quite similar; the choice between the two depends
mostly on which is more convenient in a particular situation. The former is most useful when you want to have a blob of data with callbacks to
convert it into the various data types that you advertise. When the clear_func you provided is called, you simply free the data
blob. The latter is more useful when the contents of clipboard reflect the internal state of a
Object (As an example, for the PRIMARY clipboard, when an entry widget provides the
clipboard’s contents the contents are simply the text within the selected region.) If the contents change, the entry widget can call
set_with_owner to update the timestamp for clipboard ownership, without
having to worry about clear_func being called.
Requesting the data from the clipboard is essentially asynchronous. If the contents of the clipboard are provided within the same process, then a direct function call will be made to retrieve the data, but if they are provided by another process, then the data needs to be retrieved from the other process, which may take some time. To avoid blocking the user interface, the call to request the selection, request_contents takes a callback that will be called when the contents are received (or when the request fails.) If you don’t want to deal with providing a separate callback, you can also use wait_for_contents. What this does is run the GLib main loop recursively waiting for the contents. This can simplify the code flow, but you still have to be aware that other callbacks in your program can be called while this recursive mainloop is running.
Along with the functions to get the clipboard contents as an arbitrary data chunk, there are also functions to retrieve it as text, request_text and wait_for_text. These functions take care of determining which formats are advertised by the clipboard provider, asking for the clipboard in the best available format and converting the results into the UTF-8 encoding. (The standard form for representing strings in GTK+.)
Example: Clipboard:
Copy some text before running.
public static int main (string[] args) {
Gtk.init (ref args);
Gtk.Window window = new Gtk.Window ();
window.title = "My Gtk.Clipboard";
window.border_width = 10;
window.set_default_size (300, 20);
window.destroy.connect (Gtk.main_quit);
Gtk.Entry entry = new Gtk.Entry ();
window.add (entry);
window.show_all ();
Gdk.Display display = window.get_display ();
Gtk.Clipboard clipboard = Gtk.Clipboard.get_for_display (display, Gdk.SELECTION_CLIPBOARD);
// Get text from clipboard
string text = clipboard.wait_for_text ();
entry.text = text ?? "";
// If the user types something ...
entry.changed.connect (() => {
// Set text to clipboard
clipboard.set_text (entry.text, -1);
});
Gtk.main ();
return 0;
}valac --pkg gtk+-3.0 Gtk.Clipboard.vala