New Thread

Hey folks,

This is really simple, but a little hard to explain, so bare with me.

I have a C# MDI application. On one of my child Windows there are multiple
tabs. One of the tabs is fully populated by a User Control which has on it
a 3rd party control. The 3rd party control runs very slow on semi-old PCs.
It takes about 5 or 6 seconds to load. As such, when the form is loaded, it
takes 5 or 6 seconds before the form appears.

Is there a way I can force my User Control Tab (with the 3rd party control
on it) to open on a seperate UI thread? This way the form will load and
appear right away. Only the tab with the slow control on it won't be
accessible right away.

Or, if not a seperate UI Thread, is there anything I can do to make the form
appear while the slow tab is loading?

Thx!

Herfried
Mon Jan 03 14:11:19 CST 2005

"John Smith" <js@no.com> schrieb:
> Is there a way I can force my User Control Tab (with the 3rd party control
> on it) to open on a seperate UI thread? This way the form will load and
> appear right away. Only the tab with the slow control on it won't be
> accessible right away.

UI elements that are "connected" to each other should run on the same
thread.

Is the control an old ActiveX control?

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

John
Mon Jan 03 14:18:40 CST 2005

"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
news:eH59jBd8EHA.3616@TK2MSFTNGP11.phx.gbl...
> "John Smith" <js@no.com> schrieb:
> > Is there a way I can force my User Control Tab (with the 3rd party
control
> > on it) to open on a seperate UI thread? This way the form will load and
> > appear right away. Only the tab with the slow control on it won't be
> > accessible right away.
>
> UI elements that are "connected" to each other should run on the same
> thread.
>
> Is the control an old ActiveX control?


The control is actually an Outlook Style Calendar control (I made another
posting asking if alternatives exist). It's the WinSchedule Form From
Infragistics
(http://www.infragistics.com/products/schedule.asp?sec=1&cat=2). It works
fine on newer machines, but the client has 3 year old PCs and it's very slow
on them.


>
> --
> M S Herfried K. Wagner
> M V P <URL:http://dotnet.mvps.org/>
> V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
>
>

John
Mon Jan 03 16:00:12 CST 2005


"John Smith" <js@no.com> wrote in message
news:ulDWhFd8EHA.2276@TK2MSFTNGP09.phx.gbl...
> "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
> news:eH59jBd8EHA.3616@TK2MSFTNGP11.phx.gbl...
> > "John Smith" <js@no.com> schrieb:
> > > Is there a way I can force my User Control Tab (with the 3rd party
> control
> > > on it) to open on a seperate UI thread? This way the form will load
and
> > > appear right away. Only the tab with the slow control on it won't be
> > > accessible right away.
> >
> > UI elements that are "connected" to each other should run on the same
> > thread.
> >
> > Is the control an old ActiveX control?
>
>
> The control is actually an Outlook Style Calendar control (I made another
> posting asking if alternatives exist). It's the WinSchedule Form From
> Infragistics
> (http://www.infragistics.com/products/schedule.asp?sec=1&cat=2). It works
> fine on newer machines, but the client has 3 year old PCs and it's very
slow
> on them.

Hmm....I think my problem may be more related to a need for some better
indexes on the db. I'm giving that a go and I'll see how that works for the
client.

> >
> > --
> > M S Herfried K. Wagner
> > M V P <URL:http://dotnet.mvps.org/>
> > V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
> >
> >
>
>