WPF BeginInvoke GUI Freeze

Question

0.00/5 (No votes)

See more:

hi,

i have problem in the following code:

C#

System.Threading.Thread t = new System.Threading.Thread(new System.Threading.ThreadStart(() =>
{
    Generate();
    viewer.c1DocumentViewer.Dispatcher.BeginInvoke((Action)(() =>
    {
         viewer.Report = this;
    }));
}));
t.IsBackground = true;
t.Start();

The generate function generates a Report with about 6 pages, during the generation
everything works fine and my GUI does not freeze.
But when i call BeginInvoke to set my generated Report in the Report Viewer
the whole GUI freezes for about 6 seconds.
How can i avoid freezing my gui?

Thanks in advance,
manu

Posted 1-Apr-12 4:55am

m.bleimuth

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-04-01T05:22:00

This code can be improved, but I don't think you can easily make UI more responsive. Basically, you think correctly. Just one thing: in this case, Invoke is a bit better then BeginInvoke, but I don't think you can see a big difference (but try it). Creation of a thread this way is expensive (there are three alternatives which are faster), but you did not report any observable delay before the invocation of the viewer property.

It looks like the only time-consuming operation is the rendering of the viewer content, but you the assignment should be performed through the dispatcher as you correctly do, anyway; and the rendering itself is done in a separate rendering thread.

I would experiment with the following: could you generate a new report if the same size and assign it to the viewer again. Does it take the same time? If it always the same, I would think about starting with a very short content and appending small pieces one by one from your separate thread. It would make total time even more, but could keep the UI responsive. After all, I don't know why 6 pages could be so slow. Maybe the simple reason is that the C1DocumentViewer class sucks. :-)

—SA

Clifford Nelson · Answer 2 · 2012-04-01T11:23:00

Solution 2

There is a Priority property on the Thread ([^]). I If you reduced the priority, maybe reducing the priority will help.

Posted 1-Apr-12 11:23am

Clifford Nelson

Comments

Clifford Nelson 3-Apr-12 4:39am

So I was downvoted without a comment. I am interested in knowing why priority would not work?