windows form
- Fancy Windows Forms
- Cool Vista-style Menu
- Sharing data among Windows Forms
- User Input in Windows Forms
- Application Class
- Run starts an application message loop on the current thread and, optionally, makes a form visible.
- Exit or ExitThread stops a message loop.
- DoEvents processes messages while your program is in a loop.
- AddMessageFilter adds a message filter to the application message pump to monitor Windows messages.
- IMessageFilter lets you stop an event from being raised or perform special operations before invoking an event handler.
- Passing Data between Windows Forms
- Application.DoEvents Method
- Mandelbrot in C# and Windows forms
- Data Binding Concepts in .NET Windows Forms
- Progress Bars, Threads, Windows Forms, and You
- Command Switchboard for Windows Forms
- Multi threading with Windows Forms
- The key to multi-threaded Windows Forms UI interaction
- Articles by James T. Johnson (Articles: 14)
- Popular Courses
Fancy Forms
Bring a fresh / cool look and feel to your applications.
Cool Vista style menu in your .NET applications
Data Transfer between Forms
In a Windows application, passing values from a secondary form to the main form or share data among several applications (.NET application).
Windows Forms includes a user input model based on events that are raised while processing related Windows messages. The topics in this section provide information on mouse and keyboard user input, including code examples that demonstrate how to perform specific tasks.
Provides static methods and properties to manage an application, such as methods to start and stop an application, to process Windows messages, and properties to get information about an application. This class cannot be inherited.
Remarks The Application class has methods to start and stop applications and threads, and to process Windows messages, as follows:
This article provides a simple example of using delegates and events to transfer data between Windows forms. The example provided contains three separate forms; the main form interacts with the other two forms by responding to events generated by instances of the other two forms.
In order to communicate between the forms, each of forms capable of generating an event contains declarations for a delegate and an event. A delegate may be thought of as a type safe function pointer and delegates are associated with methods that bear the same signature. An event is a device used to notify listening objects that something has happened; events are associated with a delegate when instantiated.
Processes all Windows messages currently in the message queue.
Remarks When you run a Windows Form, it creates the new form, which then waits for events to handle. Each time the form handles an event, it processes all the code associated with that event. All other events wait in the queue. While your code handles the event, your application does not respond. For example, the window does not repaint if another window is dragged on top.
If you call DoEvents in your code, your application can handle the other events. For example, if you have a form that adds data to a ListBox and add DoEvents to your code, your form repaints when another window is dragged over it. If you remove DoEvents from your code, your form will not repaint until the click event handler of the button is finished executing. For more information on messaging, see User Input in Windows Forms.
A project written in C# and Windows forms to interactively explore the Mandelbrot set
A detailed look at the concepts involved in data binding and controlling data binding
Using asynchronous progress bars on your form from start to finish
Switchboard component for user interface commands with design time support
A Windows threaded client and MVC server demonstrating interaction via XML exchange
Misc.
Teaches how to use the Invoke functionality so that interaction with UI elements can be safely done.
lot of good stuff
Popular with our users in the last month
No comments:
Post a Comment