How can i implement a message pump with winforms ?

[nicolas.hilaire]

Hi all,

i'm doing a quite long treatment in a function, and i'm showing the
progress of the treatment with a progressbar. The code is something
like this :

for each(entry in entries) // about 100 entries
{
TreatmentForOne Or2Secs();
this->progressBar1->PerformStep( );
}
during the debug, the debugger tells me that :

Managed Debugging Assistant 'ContextSwitchD eadlock' has detected a
problem in 'd:\test\NetSen dDotNet\debug\N etSendDotNet.ex e'.
Additional Information: The CLR has been unable to transition from COM
context 0x189558 to COM context 0x189408 for 60 seconds. The thread
that owns the destination context/apartment is most likely either doing
a non pumping wait or processing a very long running operation without
pumping Windows messages. This situation generally has a negative
performance impact and may even lead to the application becoming non
responsive or memory usage accumulating continually over time. To avoid
this problem, all single threaded apartment (STA) threads should use
pumping wait primitives (such as CoWaitForMultip leHandles) and
routinely pump messages during long running operations.
Specially :
To avoid this problem, all single threaded apartment (STA) threads
should use pumping wait primitives (such as CoWaitForMultip leHandles)
and routinely pump messages during long running operations.

So, how can i pumping messages ? or, should i use a thread (and how ?)
Thanks for your help
Nicolas H.

[Bruno van Dooren]

>Specially :

To avoid this problem, all single threaded apartment (STA) threads
should use pumping wait primitives (such as CoWaitForMultip leHandles)
and routinely pump messages during long running operations. So, how can i pumping messages ? or, should i use a thread (and how ?)

A more elegant solution perhaps is to use a timer.
on each elapsed timer event, process one work item. this will give your
application the chance to perform aditional message processing in between
your own processing.

this also means that your overall processing will take longer, since you are
not continuously processing your own stuff.
using a separate thread will give you a bit better performance,but requires
more coding.

pumping messages inside a message handler is something i've never tried in
..NET, so I don't know if it is possible or not.

kind regards,
Bruno.
br************* *********@hotma il.com
Remove only "_nos_pam"

[Willy Denoyette [MVP]]

Call routinely CurrentThread->Join(0), this implicitely calls
CoWaitForMultip leHandles and returns.

Willy.
<ni************ *@motorola.com> wrote in message
news:11******** **************@ o13g2000cwo.goo glegroups.com.. .
| Hi all,
|
| i'm doing a quite long treatment in a function, and i'm showing the
| progress of the treatment with a progressbar. The code is something
| like this :
|
| for each(entry in entries) // about 100 entries
| {
| TreatmentForOne Or2Secs();
| this->progressBar1->PerformStep( );
| }
|
|
| during the debug, the debugger tells me that :
|
| Managed Debugging Assistant 'ContextSwitchD eadlock' has detected a
| problem in 'd:\test\NetSen dDotNet\debug\N etSendDotNet.ex e'.
| Additional Information: The CLR has been unable to transition from COM
| context 0x189558 to COM context 0x189408 for 60 seconds. The thread
| that owns the destination context/apartment is most likely either doing
| a non pumping wait or processing a very long running operation without
| pumping Windows messages. This situation generally has a negative
| performance impact and may even lead to the application becoming non
| responsive or memory usage accumulating continually over time. To avoid
| this problem, all single threaded apartment (STA) threads should use
| pumping wait primitives (such as CoWaitForMultip leHandles) and
| routinely pump messages during long running operations.
|
|
| Specially :
| To avoid this problem, all single threaded apartment (STA) threads
| should use pumping wait primitives (such as CoWaitForMultip leHandles)
| and routinely pump messages during long running operations.
|
| So, how can i pumping messages ? or, should i use a thread (and how ?)
|
|
| Thanks for your help
|
|
| Nicolas H.
|

[nicolas.hilaire]

>Call routinely CurrentThread->Join(0), this implicitely calls

CoWaitForMulti pleHandles and returns. Willy.

Thanks willy, this is working and pumping message.
But on my form, i have a label and a progress bar.
During this time, the progress bar is refreshed, but not the label.
Should i call an explicit update ?

This is my code :
this->Show();
this->Update();
for each(entry in entries)
{
TreatmentForOne Or2Secs();
this->progressBar1->PerformStep( );
System::Threadi ng::Thread::Cur rentThread->Join(0);
}
this->Hide();

("this" is the form)

Do you know why the label isn't refreshed ?

Thanks in advance

Nicolas

[nicolas.hilaire]

maybe it's better to use Invoke or BeginInvoke

what do you think about it ?
Best, Nicolas

[Carl Daniel [VC++ MVP]]

Willy Denoyette [MVP] wrote:

Call routinely CurrentThread->Join(0), this implicitely calls
CoWaitForMultip leHandles and returns.

Is this not what Application.DoE vents was made for?

Of course, performance will be better still if the work is done on a second
thread, with UI updates sent through Control.BeginIn voke.

-cd

[nicolas.hilaire]

>Is this not what Application.DoE vents was made for?

Of course, performance will be better still if the work is done on a second
thread, with UI updates sent through Control.BeginIn voke.

I try to use BeginInvoke, but i can't undestand how it works !

I try to do something like this

ArrayList ^ GetList()
{
ArrayList ^ list = gcnew ArrayList();
BuildListInAThr eadThatTakesTim e();
return list;
}

Using Delegates and thread but i can't achieve to make it working,
because that's my first thread with the dotnet framework. If you know
how to do, or maybe a link that explains that, it will be great.

Otherwise, i will use
System::Threadi ng::Thread::Cur rentThread->Join(0);
and make a
label->update();

....

Best,

Nicolas

[Willy Denoyette [MVP]]

"Carl Daniel [VC++ MVP]" <cp************ *************** **@mvps.org.nos pam>
wrote in message news:Ox******** ******@TK2MSFTN GP14.phx.gbl...
| Willy Denoyette [MVP] wrote:
| > Call routinely CurrentThread->Join(0), this implicitely calls
| > CoWaitForMultip leHandles and returns.
|
| Is this not what Application.DoE vents was made for?
|
| Of course, performance will be better still if the work is done on a
second
| thread, with UI updates sent through Control.BeginIn voke.
|
| -cd
|
|
Not really, DoEvents was invented for VB and do pump the windows queue. The
managed wait services like Join() WaitOne() etc. do pump COM messages only
(CoWaitForMulti pleHandles ), so this solves the OP's initial problem.
However, now I see he's running this long running procedure on the UI
thread, which is of course a NO NO in windows.

Willy.

[Willy Denoyette [MVP]]

<ni************ *@motorola.com> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .
| >Call routinely CurrentThread->Join(0), this implicitely calls
| >CoWaitForMulti pleHandles and returns.
|
| >Willy.
|
| Thanks willy, this is working and pumping message.
| But on my form, i have a label and a progress bar.
| During this time, the progress bar is refreshed, but not the label.
| Should i call an explicit update ?
|
| This is my code :
| this->Show();
| this->Update();
| for each(entry in entries)
| {
| TreatmentForOne Or2Secs();
| this->progressBar1->PerformStep( );
| System::Threadi ng::Thread::Cur rentThread->Join(0);
| }
| this->Hide();
|
| ("this" is the form)
|
| Do you know why the label isn't refreshed ?
|
| Thanks in advance
|
| Nicolas
|

That means you are running your long running task on the UI thread, this is
something you should not do, run this on another thread and call Invoke or
BeginInvoke to update the progressBar, that way your UI will remain
responsive.

Willy.

[nicolas.hilaire]

>That means you are running your long running task on the UI thread, this is

something you should not do, run this on another thread and call Invoke or
BeginInvoke to update the progressBar, that way your UI will remain
responsive.

Yes, i'm running the task on the form class.

So, i'm going to use thread ... but, i just need something easy

something like this

Thread ^ t = gcnew Thread(gcnew ThreadStart(Thr eadProcess));
t->Start();
WaitForTheThrea dToTerminate();

Is this possible ? and how ?
Thanks for your help