Load gui first then read data from http remote server.

Question

0.00/5 (No votes)

See more:

Hi, My application is reading files from a server through http and it does this on the window_Initialized event. This makes it read the stuff from the remote server before the gui appear on the screen which takes like 7 seconds. So from that you start the program it takes around 7 seconds for the GUI to appear becouse of the http requests and stuff. Can I make it show the GUI first and then once the gui is loaded it does the http stuff?

Posted 17-Aug-13 0:48am

maxbre

Add a Solution

1 solution

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)

OriginalGriff · Accepted Answer · 2013-08-17T01:02:00

Yes - you just need to move the code.
One way to try is to move the coed into the Form.Shown event - that should be called once and once only, when Show or ShowDialog is called on the form. However, I haven't tried doing any long running task in there - it is possible that you still won't see anything because I am not sure if the initial Paint event has been honoured by that point - I suspect not, but would have to check.

If that doesn';t work, the better solution anyway would be to move it off the UI thread completely, and into a BackgroundWorker class instance. MSDN has details and an example, but it's pretty simple to do - the only complication is that you can't access UI controls directly from the background worker. But that would mean the UI never, ever gets "stuck" while waiting for your server, which is a much better approach.