Threading problem

[Steve]

I have a form which acts as an mdi parent. It receives an event which has a name and message
It creates a new form for every name and displays messages within that form
The event handler calls RouteMessage which dtermines if the form already exists (using a hashtable) and tries to create the form if necessary
Unfortunately, this fails with the exceptio

'Controls created on one thread cannot be parented to a control on a different thread.

So the original parent form has been created on one thread and all the events are being handled on another thread
Any suggestions as to how I might solve this

Stev
private void MonitorServer_O nMonitorEvent(o bject file, MonitorEventArg s args

RouteMessage(ar gs.serviceName, args.message)

public void RouteMessage(st ring serviceName,str ing message

if (serviceForms.C ontains(service Name)

((DisplayForm)s erviceForms[serviceName]).AddMessage(me ssage)

els

CreateNewForm(s erviceName,mess age)
public DisplayForm CreateNewForm(s tring name,string message

DisplayForm displayForm = new DisplayForm(nam e)
displayForm.Mdi Parent = this
displayForm.Sho w()
if (message != null
displayForm.Add Message(message )
serviceForms.Ad d(name,displayF orm)
return displayForm

[Jon Skeet [C# MVP]]

Steve <an*******@disc ussions.microso ft.com> wrote:

I have a form which acts as an mdi parent. It receives an event which
has a name and message. It creates a new form for every name and
displays messages within that form. The event handler calls
RouteMessage which dtermines if the form already exists (using a
hashtable) and tries to create the form if necessary. Unfortunately,
this fails with the exception

'Controls created on one thread cannot be parented to a control on a
different thread.'

So the original parent form has been created on one thread and all
the events are being handled on another thread. Any suggestions as to
how I might solve this?

As with everything UI-based, only do anything with the UI on the UI
thread which created the main window. Use Control.Invoke to invoke a
delegate on that UI thread.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Steve <an*******@disc ussions.microso ft.com> wrote:

I have a form which acts as an mdi parent. It receives an event which
has a name and message. It creates a new form for every name and
displays messages within that form. The event handler calls
RouteMessage which dtermines if the form already exists (using a
hashtable) and tries to create the form if necessary. Unfortunately,
this fails with the exception

'Controls created on one thread cannot be parented to a control on a
different thread.'

So the original parent form has been created on one thread and all
the events are being handled on another thread. Any suggestions as to
how I might solve this?

As with everything UI-based, only do anything with the UI on the UI
thread which created the main window. Use Control.Invoke to invoke a
delegate on that UI thread.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too