[Mono-dev] Mono Winforms on Mac: Clipboard patches

[stifu at free.fr]

I don't think you should use the MONO_MWF_MAC_FORCE_X11 flag to try these changes, as then you wouldn't be using the native Mac driver anymore, which means you wouldn't notice any changes before and after the patches, then.
In the first place, as Ralph was trying to get his app to work on Mono, I proposed him to look into the MONO_MWF_MAC_FORCE_X11 flag, and he replied:

"Thanks for the X11 solution tip. I tried it and it does seem more
stable but it does not support a Mac native Clipboard which is a
mandatory in my case."

----- Mail Original -----
De: "matteo tesser" <matteo.tesser at gmail.com>
À: "Miguel de Icaza" <miguel at novell.com>
Cc: "Stifu" <stifu at free.fr>, mono-devel-list at lists.ximian.com
Envoyé: Jeudi 25 Novembre 2010 00:37:15 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: Mono Winforms on Mac: Clipboard patches

Hi,
I gave a first look at the clipboard patch. I applied the patch in my
version and tried it.  Honestly I have to  say that I never saw
clipboard (copy and paste) working on WinForms/OSX, and unfortunately
I did noticed any change (but no regressions either)  in the behavior
of tests launched after the patch have been applied: this either by
setting   MONO_MWF_MAC_FORCE_X11=1 or by unsetting it.

I want to remark that the code in the static constructor of XplatUI.cs
tests only for the existence of the environment variable
MONO_MWF_MAC_FORCE_X11 but not for its value: I do not now if setting
MONO_MWF_MAC_FORCE_X11=0 is considered a valid option or not.

I will continue to look after the other changes,
Matteo

On Mon, Nov 22, 2010 at 4:00 AM, Miguel de Icaza <miguel at novell.com> wrote:
> Hello,
> I have isolated the clipboard changes from Ralph's patches, this version no
> longer regresses the API [1], and I updated the list of pending changes from
> Ralph and uploaded that [2].
> I am not sure why these changes were needed in the first place.   They moved
> the Clipboard functionality from the XplatXXX drivers into a new set of
> XplatClipboardXXX drivers, but we have no idea what was wrong with the
> previous approach and why this change is needed.   At least we now have
> those split, so we can chose to pick the changes later if they make sense,
> and we can continue integrating the rest of the patches that Ralph left on
> our doorstep one-by-one.
> [1] http://tirania.org/tmp/clipboard-patches
> [2] http://tirania.org/tmp/changes3.gz
>