Windows Forms

26-Feb-10 20:52

i have made one of my form as mdi form.
now i am trying to display other form in this form.
i want that when new form is loaded the old one hides or get closed.plz guide how to do this.
m new to win application.thanks

Re: win form

dan!sh 26-Feb-10 21:51

dan!sh

26-Feb-10 21:51

How are you opening the second form? Can you post some code?

Re: win form

mylogics26-Feb-10 21:58

26-Feb-10 21:58

on menu click i am opening the purchase form and vedor form.i want that when i open vendor/purchase form
the previously opened form get closed..

private void addNewVendorToolStripMenuItem_Click(object sender, EventArgs e)
        {
            
            Vendor frm = new Vendor();
            frm.MdiParent = this;
            frm.Show();
          
        }

        private void purchaseToolStripMenuItem1_Click(object sender, EventArgs e)
        {
            Purchase frm = new Purchase();
            frm.MdiParent = this;
            frm.Show();

        }

Re: win form

RichardM14-Mar-10 7:10

Creating an interface UI in windows forms

4-Mar-10 7:10

Before "frm.Show();", add "this.Hide();"
Unless you are looking for a modal window that blocks the old window,then I think you change "frm.Show();" to "frm.ShowModal();"

Opacity, the new Transparency.

for120625-Feb-10 7:23

for1206

25-Feb-10 7:23

Hi CP,

how to create an interface like this ?

"http://cid-038dd0e1974d763e.skydrive.live.com/self.aspx/Images/Kaspersky%20tab.JPG"

Regards,

For1206

Re: Creating an interface UI in windows forms

RichardM125-Feb-10 12:40

Re: Creating an interface UI in windows forms

25-Feb-10 12:40

Really, it is just a user drawn tab control turned on it's side.
The ball with LEDs is just an image with transparency that is in front of the tab control.
Don't mistake flashy graphics for new functionality. Big Grin | :-D

There are articles here on transparency, odd shaped controls and user drawn controls.

Opacity, the new Transparency.

BoomRShine26-Feb-10 4:03

BoomRShine

26-Feb-10 4:03

Try Windows Presentation Foundation.

.NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS) [modified]

mcrawley23-Feb-10 10:47

mcrawley

23-Feb-10 10:47

I am trying to set a .NET WinForms Control as a child to a Window/Form residing on another thread or in a different process altogether. I have had success in parenting a .NET WinForms Control to a native Win32 window in a separate process as well as a .NET WinForms Control to .NET Form residing in another process. However, when I do such to a .NET Form, the .NET form throws several exceptions when it is trying to paint the parent form. If I let the debugger catch and continue after each exception (a real "no no"), the child control finishes painting and the parent Form is left undrawn, with a big red "X" drawn in the background. Only when I create a custom UserControl and set it to the remote .NET Form does it work. What is wrong with the underlying paint procedures of several other controls in the .NET Framework for me to get this inconsistant behavior? Sample code is below...

.NET Control on a native Win32 window - WORKS FINE
// Create any WinForm control
Button button = new Button();

// Set the parent window of that control (aka window) to a common
// native Win32 window...in this case the Desktop window
Win32.SetParent(button.Handle, Win32.FindWindow("Progman", null));

// Continue running the message loop
Application.Run();

.NET UserControl on a Remote .NET Windows.Form - WORKS FINE
// Create a custom UserControl (set colors so you can see it. the
// standard UserControl has the same colors as the Form's background)
UserControl1 ctrl = new UserControl1();

// Set the parent window of that control (aka window) to a common
// .NET Form...in this case the Form1
Win32.SetParent(ctrl.Handle, Win32.FindWindow("WindowsForms10.Window.8.app.0.378734a", "Form1"));

// Continue running the message loop
Application.Run();

.NET Control on a Remote .NET Windows.Form - DOES NOT WORK
// Create any WinForm control
Button button = new Button();

// Set the parent window of that control (aka window) to a common
// .NET Form...in this case the Form1
Win32.SetParent(button.Handle, Win32.FindWindow("WindowsForms10.Window.8.app.0.378734a", "Form1"));

// Continue running the message loop
Application.Run();

Re: .NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS)

RichardM123-Feb-10 18:51

Re: .NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS)

23-Feb-10 18:51

If the form & control creation threads are different, then the event on the other thread have to be invoked. Adding a child control from a different thread fires events on the new parent thread that should be invoked. Obviously, you don't have control of the firing to make them invoked, so crash and burn.
The child draws fine, the parent, needing invoke, crashes.

Opacity, the new Transparency.

mcrawley25-Feb-10 9:40

mcrawley

25-Feb-10 9:40

When I began testing, that was my assumption going in. However, of the three code snipplets I posted, two work fine, which seem to counter your explaination. A .NET control parented to a native Win32 window in a separate process works fine as well as a .NET "UserControl" class being parented to a .NET window in a separate process. Only in select cases does your explaination seem to hold weight. Try my examples and see what you get.

Re: .NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS)

RichardM125-Feb-10 10:13

Re: .NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS)

25-Feb-10 10:13

I have a recollection that user control is special in some manner, and pointing in that direction, from MSDN:

You can host Windows Forms UserControl derived classes inside of a form, on another UserControl,
inside of Internet Explorer on a Web page, or inside a WebBrowser control hosted on a form.

[^]
I have not used user control myself, but I have hit the multiple thread problem you are talking about with other controls.
I recall the solution we had used was 'single threaded apartment' vs 'multiple threaded apartment', but I can't remember which worked correctly. I think it was single threaded, but try both and see if it changes.
Or try creating a usercontrol with a button in it and moving it to the other thread. User control may fix the threading problem for its children.
Either way, let me know how it comes out.
Thanks
Richard

Opacity, the new Transparency.

mcrawley25-Feb-10 12:08

mcrawley

25-Feb-10 12:08

The only thing special about the UserControl1 class is that I changed the background color. I could have used the UserControl class directly and set the background color. It makes no difference. In several test cases, I even added several buttons and other controls onto my derived UserControl1 class. It still works fine as a child to a Win32 or .NET WinForm in a separate process. I have learned that when ever a window (or control in .NET terms) posts a message via PostMessage(..), the active thread just adds the message to the destination's message queue and returns immediately, not waiting for the message to be processed. Had I posted a message via SendMessage(..), the active thread would suspend until the message is processed. My guess is that some of the .NET controls (like the Button control) uses SendMessage(..) somewhere internally and waits for it's child/parent to process, perhaps creating even a deadlock somewhere in worse cases. I have found articles and forums suggesting the CLR might be disposing a handle to GDI objects a the point where the exception is thrown in the internal paint procedure or the GDI handle count is exceeded. Eitherway, I am puzzled. I have found articles and code showing multithreaded windowed applications to work fine, but most developers usually have no need for such and never investigate.

Re: .NET WinForms Control as a child to a Window residing in a different process (MIXED RESULTS)

RichardM125-Feb-10 12:34

25-Feb-10 12:34

That makes sense.
I don't know where I heard or read about UserControl being special, but this reinforces it.
I'd say that they did decouple cross thread calls in userControl.
We have an app that every window has a thread that actually creates and opens the form.
It also makes tabs by taking the contents of an existing form and sticking it into a new TabControl.
Don't ask why, it's a long story Smile | :)

While we were initially working on it, we would get cross thread exceptions.
We changed some of the windows to be single threaded apartment, and the problem went away.
We were having problems with the clipboard that also went away when we did STA.
This should also may help me. We are doing much to deal with this problem is other areas. UserControl as the top level container looks like it could let us get rid of some code.
Thanks
Richard

Opacity, the new Transparency.

desktop application

mylogics22-Feb-10 19:34

22-Feb-10 19:34

hii all
m new to windows application.I want to create a desktop application but dont have idea
where to start with.Can anybody give me any gud link or tutorial or name of ebooks which would
help me in my project.however i have worked on web application(asp.net using csharp).plz guide me ...thanks..

Andy_L_J22-Feb-10 20:06

Andy_L_J

22-Feb-10 20:06

You could check out any one of the results here:

Windows Forms Application Tutorials[^]

or search for the MSDN videos.

I don't speak Idiot - please talk slowly and clearly

'This space for rent'

Driven to the arms of Heineken by the wife

BoomRShine23-Feb-10 3:53

BoomRShine

23-Feb-10 3:53

Download Visual C# 2008 Express Edition.

http://www.microsoft.com/express/Downloads/#2008-Visual-CS[^]

Install, launch, and register (Help -> Register Product). After you register, you'll be eligible for some freebies, including the book (PDF) "Microsoft Visual C# 2008 Express Edition - Build a Program Now!". Download that, and it should help get you started.

Abhinav S26-Feb-10 22:27

Abhinav S

26-Feb-10 22:27

You could start by going through some good C# books.

Me, I'm dishonest. And a dishonest man you can always trust to be dishonest.
Honestly. It's the honest ones you want to watch out for...

mylogics26-Feb-10 22:33