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

Daniel Morgan danmorg@sc.rr.com
Fri, 21 Mar 2003 08:19:43 -0500

Thee Control.Name can be used for comparison purposes by the application

For instance, a programmer could iterate through a collection of controls
looking for a TextBox Control named "User ID", if that control is found, it
will be enabled and colored yellow for required entry; otherwise, it will
remain disabled and grayed.

The Control.Name is the the property (Name) that is used to identify a
control in the Visual Studio.net designer properties.  Once a control is
dropped on to the windows form, if you change the (Name) property of the
control, Visual Stuido.net will update the variable name in the C# source

For example:, if you change the (Name) from TextBox1 to userIdTextBox,
it will be updated in code:

private System.Windows.Forms.TextBox userIdTextBox;

Indicates the name used to identify the object.

-----Original Message-----
From: mono-winforms-list-admin@lists.ximian.com
[mailto:mono-winforms-list-admin@lists.ximian.com]On Behalf Of Aleksey
Sent: Friday, March 21, 2003 7:57 AM
To: mono-winforms-list@lists.ximian.com
Subject: Re: [Mono-winforms-list] Introduction, patching, canonization,

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.


Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
Mono-winforms-list maillist  -  Mono-winforms-list@lists.ximian.com