[Mono-winforms-list] Re: question about mono <-> ms .net

Jordi Mas jordi@ximian.com
Mon, 03 Jan 2005 18:28:08 +0100

El dl 03 de 01 del 2005 a les 11:16 -0500, en/na Erik Dasque va
> Hi Dariusz,
> the best forum to answer that question is probably the Windows Forms 
> mailing list.
> Erik
> On Dec 13, 2004, at 9:58 AM, franz777@o2.pl wrote:
> > Hello,
> >
> > I'm a programmer, who writting .net windows forms application (in
> > c#), and I want my application to work under Mono in Linux. I have
> > re-written much of my application to avoid windows p/invoke calls
> > and other dll's binding in our program. But I've an important
> > question: I am using a WndProc (overriden) routine because I must
> > intercept for example non-client title bar clicks, double click,
> > etc... So my program expects (and that is done by windows) that I
> > intercept WM_NCLBUTTONDBLCLK message in WndProc (0x00A3 event) when
> > user double click on titlebar (non-client area). There is no other
> > method in .NET library to intercept such kind of tasks... My
> > question is: will MONO support windows messages mapping? When under
> > MONO user double click titlebar, will MONO send to my app message
> > with code 0x00A3 via WndProc? I hope that will be happened... But if
> > not, please tell me how to write such chunks of code to be portable
> > to MONO ?
> > Please, answer to my questions...

We are currently completing a new implementation of System.Windows.Forms
written completely on the top of the System.Drawing namespace and using
a small layer for every operating system (for windowing, keyboard,
mouse, and so on).

We do support WndProc and its related support infrastructure. In Linux,
we convert X11 events into WndProc alike messages. I mean, a .Net
application get WM* messages as expected. As you can imagine, every
event has to be coded and test it in different platforms.

We currently do not support what you need, but you have all the
System.Windows.Forms source code available under an open source license
and you are free to contribute the parts that you need and we can
provide you some help point out what has to be done and how.

For a more detailed information of the current status of our
System.Windows.Forms you can visit http://www.mono-



Best Regards,


Jordi Mas i Hernāndez - Mono development team - http://www.mono-project.com
Homepage and LiveJournal at http://www.softcatala.org/~jmas