WPF Control Visibility and Button Click Lifecycle

Question

0.00/5 (No votes)

See more:

How can I make the progessbar visible, then check the connection, then make the progressbar hidden. In that Order!

private void button_Click(...)
{
    progBar.Visibility = Visibility.Visible;
    CheckTheConnection();
    progBar.Visibility = Visibility.Hidden;
}

If I remove the Hidden attribute, the CheckConnection runs then the progBar becomes visible. This is the opposite of what I want.

Posted 19-Jan-11 12:34pm

hrdfsique

Updated 19-Jan-11 12:35pm

v2

Add a Solution

3 solutions

Solution 4

http://www.wpf100.com/html/5/2012-04/article-215.html

Posted 11-May-12 17:15pm

sxliusir

Updated 11-May-12 18:17pm

v2

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)

#realJSOP · Accepted Answer · 2011-01-19T12:41:00

Solution 1

Put the code in CheckConnection into a thread, and then display/update the progressbar via appropriate mechanisms (Invoke).

Posted 19-Jan-11 12:41pm

#realJSOP

Comments

Nish Nishant 19-Jan-11 19:09pm

Voted 5, proposed as answer.

hrdfsique 19-Jan-11 19:59pm

OK, so not as simple as I thought.

Threading seems like it could be a great solution but I am running into a problem that is a bit out of my scope.

I am working on a user control that accepts textBox inputs to create the SQL connection string. The textbox inputs are assigned to Dependancy Properties, whis isn't such a big deal because I could just reassign them in the new thread. Problem is that I can not get the textbox values into the new thread because they are still handled by the main thread.

I'm not sure what to do.

Venkatesh Mookkan 19-Jan-11 21:26pm

I too propose this as Answer

hrdfsique 21-Jan-11 19:03pm

Threading is definitely the answer, but after doing much more research... The best method to use in my case is the BackGroundManager Class.

Nish Nishant · Accepted Answer · 2011-01-19T14:12:00

Solution 3

Based on your reply to John, it seems you need to get a basic understanding on how to use threads from WPF. This is a good article on the topic:

http://msdn.microsoft.com/en-us/magazine/cc163328.aspx[^]

Notice how accessing members across the threads is not that complex (although you do need to be careful).

Posted 19-Jan-11 14:12pm

Nish Nishant

Updated 19-Jan-11 14:14pm

v3

Comments

Venkatesh Mookkan 19-Jan-11 21:26pm

Useful share. Thanks Nishant

Espen Harlinn 20-Jan-11 14:00pm

5+ A solid improvement, the article privides all the required information

Nish Nishant 20-Jan-11 14:05pm

Thank you, Espen.

hrdfsique 21-Jan-11 19:03pm

This article did not sufficiently answer my question. After searching "Thread" through the MSDN, the BackgroundManager has the better capability for this particular problem.

Nish Nishant 21-Jan-11 21:31pm

I don't know what you mean by BackgroundManager. There is a BackgroundWorker class and this class has been well explained in the article I linked to. Anyway glad to hear you've worked it out. Thanks.