[C#]
Form form1 = new Form();
Bitmap bmp = imageList1.Images[index] as Bitmap;
form1.Icon = Icon.FromHandle(bmp.GetHicon());
[VB.NET]
Dim form1 As Form = New Form()
Dim bmp As Bitmap = imageList1.Images(index) as Bitmap
form1.Icon = Icon.FromHandle(bmp.GetHicon())
Please refer to the sample attached here that illustrates this.
To do this, you can use use iterop to access the GetSystemMenu and AppendMenu Win32 APIs. You also need to override the form’s WndProc method to catch and act on the menu message. This idea was posted in the Microsoft newsgroups by Lion Shi. Here are some sample projects.
One way to do this is to make the TextBox either a public property or a public field. Then you will be able to access it through the instance of its parent form. So, if TextBox1 is a public member of FormA and myFormA is an instance of FormA, then you can use code such as
[VB.NET]
Dim strValue as String = myFormA.TextBox1.Text
[C#]
string strValue = myFormA.TextBox1.Text;
anywhere myFormA is known. Here is a VB project illustrating this technique.
One way to do this is to override the form’s WndProc method and check for WM_SYSCOMMAND and SC_CLOSE. Looking for WM_CLOSE in the override is not sufficient as WM_CLOSE is seen in both cases. A sample is available for download (C#, VB).
publicconstint SC_CLOSE = 0xF060;
publicconstint WM_SYSCOMMAND = 0x0112;
//_closeClick is a bool member of the form initially set false...// It can be tested in the Closing event to see how the closing came about.protectedoverridevoidWndProc(ref System.Windows.Forms.Message m)
{
if(m.Msg == WM_SYSCOMMAND && (int)m.WParam == SC_CLOSE)
this._closeClick = true;
base.WndProc(ref m);
}
You can use the System.Reflection.Assembly.CreateInstance method to create a form from its name. Below is a code snippet. The name in the textbox has to be the full name including its namespace. So if there is a class named Form2 in namespace MyCompanyName, then the textbox would contain MyCompanyName.Form2. This snippet also assumes that the class is defined in the current executing assembly. If not, you would have to create an instance of the assembly that contains the class instead of calling the static method GetExecutingAssembly. As noted on this board, using reflection in this manner might affect performance.
Shawn Burke responded to this question in a posting on microsoft.public.dotnet.framework.windowsforms newsgroup.
There is not currently a way to do this built into the framework, but WM_SETREDRAW will do what you’re looking for. It can’t be called recursively, so here’s code for a property you can add to your form to handle it. A VB sample is also available.
int paintFrozen;
privateconstint WM_SETREDRAW = 0xB;
[DllImport(''User32'')]
privatestaticexternboolSendMessage(IntPtr hWnd, int msg, int wParam, int lParam);
privatebool FreezePainting
{
get { return paintFrozen > 0; }
set {
if (value && IsHandleCreated && this.Visible)
{
if (0 == paintFrozen++)
{
SendMessage(Handle, WM_SETREDRAW, 0, 0);
}
}
if (!value)
{
if (paintFrozen == 0)
{
return;
}
if (0 == --paintFrozen)
{
SendMessage(Handle, WM_SETREDRAW, 1, 0);
Invalidate(true);
}
}
}
}
This problem is discussed in an article in the .NET docs. Search for ‘Setting a Form to Be Invisible at Its Inception’. The idea is to startup the application in a different module than your main form. Then the application and main form can have independent lifetimes. Sample code is given in the referenced article.
One way to do this is to maintain a list of opened modeless dialogs and check this list before you open a new one to see if one is already present. If you open all these modeless dialog’s from the same ‘main’ form, then you can use the Owned Forms property of that main form to maintain this list of opened dialogs. Below are some code snippets that suggest how you must go about this. Note that your dialog forms need to be able to turn off the ownership. This is done below by adding an Owner field to the dialog form.
//sample code that either opens a new dialog or displays an already opened dialog private void button1_Click(object sender, System.EventArgs e)
{
foreach (Form f inthis.OwnedForms)
{
if (f is Form2)
{
f.Show();
f.Focus();
return;
}
}
//need a new one
Form2 f2 = new Form2();
this.AddOwnedForm(f2);
f2.Owner = this;
f2.Show();
}
//code for form2 publicclassForm2 : System.Windows.Forms.Form
{
private System.Windows.Forms.Label label1;
public Form Owner;
//.............. private void Form2_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
Owner.RemoveOwnedForm(this);
}
}
The opacity property enables you to specify a level of transparency for the form and its child controls.
The TransparencyKey property will let you make the form transparent while keeping it’s child controls visible (provided they have a different BackColor).
See the .NET documentation for Form.Opacity for differences between Opacity and TransparencyKey properties.
You can listen to the Form’s Closing event, where you can display a MessageBox as show below:
[C#]
privatevoidForm1_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
if (MessageBox.Show('Do you want to close the application?', 'Close Application', MessageBoxButtons.YesNo) == DialogResult.No)
e.Cancel = true;
}
[VB.NET]
Private Sub Form1_Closing(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs)
If MessageBox.Show('Do you want to close the application?','Close Application',MessageBoxButtons.YesNo) = DialogResult.No Then
e.Cancel = True
End If
End Sub
The following code snippet demonstrates how you can make your form cover the whole screen including the Windows Taskbar.
[C#]
// Prevent form from being resized.this.FormBorderStyle = FormBorderStyle.FixedSingle;
// Get the screen bounds
Rectangle formrect = Screen.GetBounds(this);
// Set the form’s location and sizethis.Location = formrect.Location;
this.Size = formrect.Size;
[VB.NET]
’ Prevent form from being resized.
Me.FormBorderStyle = FormBorderStyle.FixedSingle
’ Get the screen bounds
Dim formrect As Rectangle = Screen.GetBounds(Me)
’ Set the form’s location and size
Me.Location = formrect.Location
Me.Size = formrect.Size
You can restrict the size of a form by setting it’s MaximumSize and MinimumSize properties. This will help you control the maximum and minimum size the form can be resized to. Also note that WindowState property of the form plays a part in how the form can be resized.
[C#]
//Minimum width = 300, Minimum height= 300this.MinimumSize = new Size(300, 300);
//Maximum width = 800, Maximum height= unlimitedthis.MaximumSize = new Size(800, int.MaxValue);
[VB.NET]
’Minimum width = 300, Minimum height= 300
Me.MinimumSize = New Size(300, 300)
’Maximum width = 800, Maximum height= unlimited
Me.MaximumSize = New Size(800, Integer.MaxValue)
Your main form is an object of type System.Windows.Forms.Form. Use its Close method to exit the application. If you wish to Exit from a Form’s constructor, this will not work. A workaround is to set a boolean flag that you can later check in the Form’s Load method to call Close if required.
Another way is to use the Application.Exit() method.
The framework automatically resizes the form if the current Font size during runtime is different from the font size in design-time. It however doesn’t auto size when the resolution changes. But it should be easy for you to accomplish. You could derive a custom Form, provide a ‘ScreenResolutionBase’ property that could return the current screen resolution (Screen.PrimarScreen.Bounds will give you this). This value will get serialized in code during design time. Then during runtime in the Form’s OnLoad you could check for the current screen resolution and resize the Form appropriately.
Make your main form the ‘Owner’ of the form in question. Refer to Form.Owner in class reference for more information.
[C#]findReplaceDialog.Owner = this; // Your main form.findReplaceDialog.TopLevel = false;[VB.Net]findReplaceDialog.Owner = Me ’ Your main form.
findReplaceDialog.TopLevel = False
In the Solution Explorer window, you’ll see a file called app.ico in your project. This file contains your application icon. You can change this to a different file in the project properties screen which you see by right-clicking the project node in the Solution Explorer, and selecting Properties..
Make sure you implemented and executed code similar to the InitializeComponent method that VS adds to your Windows Forms project for controls added during design time. Recall that InitializeComponent() is called from your Forms constructor to create the controls, size, position and show the controls, and finally add the controls to the form’s Controls collection. So, your code at runtime should also implement these same steps. In particular, don’t forget the this.Controls.AddRange call that adds your new controls to the form’s Controls collection.
One way is to place all the controls into a single GroupBox and then use the GroupBox.Enabled property to manage whether the controls are editable or not.
Use the Form.FormBorderStyle property to control a form’s border.
publicvoidInitMyForm()
{
// Adds a label to the form.
Label label1 = new Label();
label1.Location = new System.Drawing.Point(80,80);
label1.Name = 'label1';
label1.Size = new System.Drawing.Size(132,80);
label1.Text = 'Start Position Information';
this.Controls.Add(label1);
// Changes the border to Fixed3D.
FormBorderStyle = FormBorderStyle.Fixed3D;
// Displays the border information.
label1.Text = 'The border is ' + FormBorderStyle;
}
See the Control.Handle property which returns the HWND. Be careful if you pass this handle to some Win32 API as Windows Forms controls do their own handle management so they may recreate the handle which would leave this HWND dangling.
(from sburke_online@microsoft..nospam..com on microsoft.public.dotnet.framework.windowsforms)