[Mono-winforms-list] Introduction, patching, canonization, roadmap.

[Alexandre Pigolkine]

Completely agree with this.

We need to register several window classes, but not all of
them are connected to Form.

And, IMHO, Conrol.Name gives ability to find control by name,
and not to define Window class name.

Aleksey:
I checked-in your code but only today noticed one problem.
You moved WM_*SCROLL handling to the Control.cs,
but this breaks *ListBox controls. They receive a message
with LParam = 0, so I made a quick fix:

case Msg.WM_HSCROLL:
case Msg.WM_VSCROLL:
if(!Control.ReflectMessage( m.LParam, ref m )) {
CallControlWndProc(ref m);
}
break;

Is it ok so for your purposes ?

Alexandre

----- Original Message -----
From: "Aleksey Ryabchuk" <ryabchuk@yahoo.com>
To: <mono-winforms-list@lists.ximian.com>
Sent: Friday, March 21, 2003 1:57 PM
Subject: Re: [Mono-winforms-list] Introduction, patching, canonization,
roadmap.


> Regarding the patch, I find it quite controversial.
> The movement of class registration from
> ScrollableControl to Form will break working of some
> other controls at the moment - Panel in particular. I
> also don't think that Control.Name property actually
> represents the name of the window class.
>
> regard
> ary
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
> _______________________________________________
> Mono-winforms-list maillist  -  Mono-winforms-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
>