Re: Does Application.UseWaitCursor affect all threads in an application
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Tue, 04 Dec 2007 11:56:35 -0800
On Tue, 04 Dec 2007 10:21:44 -0800, Academia <academiaNOSPAM@xxxxxxxxxx> wrote:
Paldino and Machin, thanks for replying.
Normally I'd reply to each of you but I'll save bandwidth and do it only
once since the replies are identical.
Please excuse the VB. The original question was not language specific. And I don't believe this is either.
Well, you _are_ posting in the C# newsgroup after all.
As much as the community here is very flexible with respect to whether a question is truly C# specific (at least half the questions here really aren't C# questions), it seems to me that it's not unreasonable to insist that C# be at least _somehow_ connected to the question. If you're coding in VB, I'd say that's a really good sign you need your question asked and answered elsewhere.
The second thread form only shows a progress bar which get updated via a
sub:
[VB snipped]
Is there something wrong with this.
No, that's the "marshaling" that Nicholas is talking about (using Control.Invoke()).
Pete
.
- Follow-Ups:
- References:
- Prev by Date: XML Serialization issue
- Next by Date: RE: Sending Binary files with C# Apps
- Previous by thread: Re: Does Application.UseWaitCursor affect all threads in an application
- Next by thread: Re: Does Application.UseWaitCursor affect all threads in an application
- Index(es):
Relevant Pages
|
