Changes between Version 12 and Version 13 of Clipboard

Timestamp:

05/22/13 03:20:48 (8 years ago)

Author:

Antoine Martin

Comment:

match code refactoring and updates

Clipboard

@@ -8 +8 @@
 Clipboard support is an ongoing struggle.
 One common difficulty with Windows clients is that these platforms only have a single (*) clipboard whereas X11 has three ({{{CLIPBOARD}}}, {{{PRIMARY}}} and {{{SECONDARY}}}), and therefore we need to choose which one to exchange with.
-This can be changed at runtime via the tray menu. (see also #272)
-Another Windows-specific problem is to do with the way it pulls clipboard data as soon as we claim ownership of the selection (see workaround in r3051 + r3075)
-On OSX, I cannot find any good asynchronous clipboard API, the clipboard is simply not implemented there yet (see #11)
+On MS Windows, the OS pulls clipboard data as soon as we claim ownership of the selection (see workaround in r3051 + r3075)
+On OSX, I cannot find any good asynchronous clipboard API, the clipboard is synchronizing only in one direction (server to client, see #11)
 
-A more technical issue is to do with the way the clipboard hooks are implemented, using native C code ([/browser/xpra/trunk/src/wimpiggy/gdk/gdk_atoms.pyx wimpiggy.gdk.gdk_atoms] Cython code imported in [/browser/xpra/trunk/src/xpra/platform/gdk_clipboard.py xpra.platform.gdk_clipboard]) and [/browser/xpra/trunk/src/xpra/nested_main.py nested main loops].
+A more technical issue is to do with the way the clipboard hooks are implemented, using native C code ([/browser/xpra/trunk/src/xpra/gtk_common/gdk_atoms.pyx xpra.gtk_common.gdk_atoms] via Cython, which is imported in most platform specific clipboard implementations and also the [/browser/xpra/trunk/src/xpra/gtk_common/nested_main.py nested main loop] code.
 
 
@@ -35 +34 @@
 Starting with v0.9.0 there is also a tool which can be used to diagnose clipboard behaviour:
 * {{{GTK_Clipboard_Test.exe}}} on win32
-* {{{xpra/gtk_view_clipboard.py}}} on posix
+* {{{gtk_view_clipboard.py}}} on posix
 see [/ticket/272#comment:5 #272 comment:5] for screenshots and help with that.