, for whatever
reason. Does the clipboard manager of KDE work that different?
Btw. I'm testing with VirtualBox.
Marvin
Quintus schrieb:
Thank you!
Marvin
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info
Hi all,
I managed to get it work now! Many thanks to you all, without the
resources you pointed me to I wouldn't have been able to finish this.
So, here's the code:
-
/*
*call-seq:
* Clipboard.write(clipboard, text) == nil
*
*Writes +text+ to the
Hi Glynn,
Apart from implementing the CLIPBOARD selection, the application
should implement the SAVE_TARGETS protocol for optimum behaviour with
modern clipboard managers. For details, see:
OK, I've done so (hopefully).
http://www.freedesktop.org/wiki/ClipboardManager
After rereading this
Hi,
If you can, try it under gnome too
That's quite easy to do - I'm already working under GNOME, I never tried
KDE.
as the last time I worked with any
clipboard code, I found its clipboard manager more cooperative at saving
non-standard data-types than when testing under KDE.
Is text a
I think I'm facing a window manager problem. When I try to get into how
the GTK functions solve the CLIPBOARD problem and even if I could
implement this in my function: If somebody now tries this on a KDE
distro like Kubuntu or openSUSE or on one with Xfce - that wouldn't
work. It seems like I
Hi there,
OK, this is kind of a longer story. Since ~4 weeks I'm trying to create
a C extension for the Ruby programming language (I'm sure you don't have
to know Ruby to answer this question, since it's almost C code) that
allows to read from and write to the X clipboards. I've searched through
