What is the best way to do this...

[PiotrKolodziej]

Hi
1. app start
2. user clicks Login Button
3. Application connects to the serwer ( check login and download dir list -
1mb )
Problem is when application is executing method responsible for dooing 3.
It takes time and i dont want my app to be "lagged".
I tought that i can create thread for this task. When thread will finish the
only thing that remains is to fill treewiev in main thread ( so i need to
invoke one method ).
is this good solution?

[Michael Nemtsev]

Hello PiotrKolodziej,

This is reasonable solution, because main thread is not that place where
task shoul be run

In you main window you can show the progress bar informing your user how
long is remained to download

PHi
P1. app start
P2. user clicks Login Button
P3. Application connects to the serwer ( check login and download dir
Plist -
P1mb )
PProblem is when application is executing method responsible for
Pdooing 3.
PIt takes time and i dont want my app to be "lagged".
PI tought that i can create thread for this task. When thread will
Pfinish the
Ponly thing that remains is to fill treewiev in main thread ( so i
Pneed to
Pinvoke one method ).
Pis this good solution?
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

[Nicholas Paldino [.NET/C# MVP]]

PiotrKolodziej,

Well, it's your only solution really. How come it takes so long to
download the directory list?

But generally, yes, you should invoke another thread to do this and then
notify your main app when it is complete.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"PiotrKolodziej" <pi*************@gmail.comwrote in message
news:5a***************************@news.chello.pl. ..

Hi
1. app start
2. user clicks Login Button
3. Application connects to the serwer ( check login and download dir
list - 1mb )
Problem is when application is executing method responsible for dooing 3.
It takes time and i dont want my app to be "lagged".
I tought that i can create thread for this task. When thread will finish
the only thing that remains is to fill treewiev in main thread ( so i need
to invoke one method ).
is this good solution?

[PiotrKolodziej]

Thank you both.
I also need progress bar because of long time that is takes.
I tought i can call thread. Inside this thread create instance of
ProgressBarForm to display progress.
When login and download will complete i will dispose this form and Invoke
another method to let Main thread know that job is done.

Iam writing this because i have still in my mind other solution. Instead of
calling thread i can explicitly create instance of another Form ( with
progress bar and download methods ) and let the Main form know from new this
new Form if the job is done.

I'd like to know your opinion.
PK

[Bruce Wood]

PiotrKolodziej wrote:

Thank you both.
I also need progress bar because of long time that is takes.
I tought i can call thread. Inside this thread create instance of
ProgressBarForm to display progress.
When login and download will complete i will dispose this form and Invoke
another method to let Main thread know that job is done.

Iam writing this because i have still in my mind other solution. Instead of
calling thread i can explicitly create instance of another Form ( with
progress bar and download methods ) and let the Main form know from new this
new Form if the job is done.

Simply creating a second form will not make a difference if the
download is still happening on the UI thread. If the UI thread is
waiting for the download, it cannot be redrawing anything on the
screen, so your application will freeze.

No matter how you slice it, you need a background thread if you want
your application to remain responsive (and that includes drawing a
progress bar).

[PiotrKolodziej]

>

Simply creating a second form will not make a difference if the
download is still happening on the UI thread. If the UI thread is
waiting for the download, it cannot be redrawing anything on the
screen, so your application will freeze.

No matter how you slice it, you need a background thread if you want
your application to remain responsive (and that includes drawing a
progress bar).

I didn't mention that i will wait for the Second form to complete. I might
simply Show() not ShowDialog(), and let the Main thread go...

[Bruce Wood]

PiotrKolodziej wrote:

Simply creating a second form will not make a difference if the
download is still happening on the UI thread. If the UI thread is
waiting for the download, it cannot be redrawing anything on the
screen, so your application will freeze.

No matter how you slice it, you need a background thread if you want
your application to remain responsive (and that includes drawing a
progress bar).

I didn't mention that i will wait for the Second form to complete. I might
simply Show() not ShowDialog(), and let the Main thread go...

I doesn't matter whether you use Show() or ShowDialog(). The two forms
are both running on the UI thread. If you do the download from any form
you will block the entire UI.