Re: Component calling a form
From: Mike Hildner (mhildner_at_afweb.com)
Date: 03/15/04
- Next message: Anthony Nystrom: "Question on Len function...."
- Previous message: Anthony Nystrom: "mscorlib continued...."
- In reply to: Mike Hildner: "Component calling a form"
- Next in thread: spamfurnace: "Re: Component calling a form"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 14:59:57 -0700
Well, for now, I'm getting around this by creating a new thread, then doing
Form.ShowDialog and it seems to be ok. Still seems like I'm missing
something :(
"Mike Hildner" <mhildner@afweb.com> wrote in message
news:%23sxyHwrCEHA.2556@TK2MSFTNGP12.phx.gbl...
> I've created a class library and a component. The component just waits
until
> a UDP message arrives. What I'd like to do is when I get a message is show
a
> form that has the data that UdpClient.Receive returns.
>
> So I created a Windows form, with a single text box, in the class library.
> If I attempt to show the form with Form.Show() my application becomes "Not
> Responding". If I start a thread to show the form, the form just flashes
> briefly. If I use Form.ShowDialog() things seem to work ok, except that
only
> one form at a time will show if there are several messages. Closing the
form
> then brings up the next message.
>
> I assume I'm doing something wrong by trying to show a form from a
> component, but don't really know. Can anyone suggest how to do this
> properly?
>
> Thanks,
> Mike
>
>
- Next message: Anthony Nystrom: "Question on Len function...."
- Previous message: Anthony Nystrom: "mscorlib continued...."
- In reply to: Mike Hildner: "Component calling a form"
- Next in thread: spamfurnace: "Re: Component calling a form"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
