Version: (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux Hey, I just read that article http://www.kdedevelopers.org/node/1787 about klipper as i was wondering that some clipboard content gets "lost" or isn't even recognized by klipper... well know that i know how the X-Clipboard works i was wondering whether it's possible to show the current owner of the clipboard? The thing is.. i was confused for example that when copying image-data from kolourpaint Klipper said the clipboard was empty. As far as I know the X-Clipboard supports information for Mime-types, doesn't it? So it would be cool if klipper at least could inform me, what the current clipboard-content's type is - or better: who the current clipboard owner is.. i.e. show "image/png from kolourpaint" (maybe in italics as it will get lost in history due to copying only textual contents) in the first row of klippers menu. By the way, thanks for Klipper anyway - I'd even say it's the tool i'm missing most when working in non-KDE-environments (-:
damn, i should re-read the title of my postings.. "poll on demand" -> clicking that item in klipper would make it non-italic -> save in history / poll and save. I think that would temporarily offer more features and avoid some problems with clipboard-dataof non-textual type.
I agree the text is inaccurate (it's the clipboard history that is empty, not the clipboard(s)), but I am not sure I'd wish to have entries that Klipper cannot actually honor. I'll think a bit about it. P.S: You can turn on the support for images. I'd appreciate bug reports for that feature in any case.
It's a cool idea, but given the lack of movement for so long, I think this is unlikely to be implemented unless someone submits a merge request to do it. Accordingly, I'm going to close this request so that the list of requested features better reflects work in progress or under active consideration. This doesn't mean that the idea is being vetoed, just that there aren't resources to consider implementing it absent volunteer contributions to do so--for which no formal feature request is needed. Thanks for understanding!