Form freezes while executing command

Question

1.00/5 (1 vote)

See more:

I am developing software with OCR function for a client. I am using Visual studio 2012. Everything works fine except the part where OCR functionality is called. Winform is frozen for 10 or 15 sec and after that everything is OK again (I can move my mouse and click on form buttons again. Is there a way to make OCR function work separate from main form ?

Posted 15-Apr-13 5:01am

Alessio Piazza

Add a Solution

Comments

[no name] 15-Apr-13 11:02am

Yes it's called "threading"

Sergey Alexandrovich Kryukov 15-Apr-13 11:13am

That's right :-). I answered in detail, please see.
—SA

2 solutions

Solution 2

You are doing everything in the main thread most proably and that’s why GUI freezes. You need to start a new background thread for the processing you want to do.

You can find more information here:
http://msdn.microsoft.com/en-us/library/system.threading.parameterizedthreadstart.aspx[^]

Posted 15-Apr-13 6:04am

Billy-TheKing

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 · Accepted Answer · 2013-04-15T05:13:00

What do you expect? You make your UI thread busy with lengthy operation, why could you expect some UI activity? By miracle? :-)

And this is not related to a form. Why do you think that forms work independently?

You need to execute all blocking or lengthy operations in a separate thread, other then UI, to keep UI responsive. The only problem is: you cannot call anything related to UI from non-UI thread. Instead, you need to use the method Invoke or BeginInvoke of System.Windows.Threading.Dispatcher (for both Forms or WPF) or System.Windows.Forms.Control (Forms only).

You will find detailed explanation of how it works and code samples in my past answers:
Control.Invoke() vs. Control.BeginInvoke()[^],
Problem with Treeview Scanner And MD5[^].

See also more references on threading:
How to get a keydown event to operate on a different thread in vb.net[^],
Control events not firing after enable disable + multithreading[^].

—SA