Re: X11 Selections

[Alexander Gottwald <Alexander dot Gottwald at s1999 dot tu-chemnitz dot de>]

Harold L Hunt II wrote:

> Actually, we can break this into two pieces like the Win32->X11 part
> below by calling SetClipboardData (foo, NULL)... this tells Windows that
> we are delaying rendering the copied text/image/whatever and we must
> process WM_RENDERFORMAT and WM_RENDERALLFORMATS to do the actual copying
> if the data is ever pasted within Windows.
>
> This is great because it prevents copying text over the wire that will
> never be pasted, and it sets us up to handle images and other things
> that we do not currently handle.

This is something I was still searching in the MSDN.

> >  If every change of the selection is indicated by XSetSelectionOwner then
> >  we always place the copy of the selection in the clipboard.
>
> I think we always get an XSetSelectionOwner call, but lets try to delay
> the actual copying until later, as I mentioned above.
>
> > Win32->X11
> >
> >  Win32 client copies to the clipboard
> >
> >   - WindowProc receives WM_DRAWCLIPBOARD
> >   - call ProcSetSelectionOwner with RootWindow (or fake window) as owner
>
> Yes, that is good.
>
> >  X11 client calls XConvertSelection
> >
> >   - receive SelectionRequest event
> >   - translate clipboard data for xclient
> >   - send data to client
>
> Right.  This is exacly like I mentioned above for delaying the copying
> in the X11->Win32 path.
>
> Sounds like we have a good plan for implementing the next version of
> clipboard integration.

This sounds great.

bye
    ago

NP: Placebo - Ask for answers
-- 
 Alexander.Gottwald@informatik.tu-chemnitz.de
 http://www.gotti.org           ICQ: 126018723