Here's an example of what I'm talking about--and how it's not wanting to
keep track of nothing--it's just giving the user the impression that
something is still happening when I can't keep track of exactly how much is
getting done per amount of time manually--just a little fascade for them...
************CODE*****************
frmMain frmParent = (frmMain)this.TopLevelControl;
frmParent.SetProgressBarValue(50, true);
frmParent.SetStatusBarText("Retrieving Unmapped Product records...", true);
DataSet ds = boProductClientLoadView.GetDataSet();
************************************
frmParent.SetProgressBarValue(75, true);
frmParent.SetStatusBarText("Loading data into grid...", true);
ugUnmappedProducts.DataSource = ds.Tables[0];
**************************************
frmParent.SetProgressBarValue(100, true);
frmParent.SetStatusBarText("Complete.", true);
****************************************
The starred lines are examples of lines of code where work is being done by
the app, but I can't track it. So what I want to happen is have a timer
tick away every second or two and just jump that progress bar up 1% each
time so the user thinks/knows that SOMETHING is happening still. Otherwise
it kind of looks like the app just froze on 50% or 75% while it does its
thing.
To Peter:
That sounds like a brilliant plan and one that I would immediately try
to implement if we weren't still trying to talk the boss-man into plunking
down the extra coin to upgrade us from VS 2003 to 2005. Is there anything
that would accomplish the same thing in 2003?
Thanks :).
-Jayyde
"iwdu15" <jmmgoalsteratyahoodotcomwrote in message
news:0A**********************************@microsof t.com...
well it doesnt make sense to have a progressbar keep track of nothing,
maybe
you should rethink ur UI....just my 2 cents, but show us your code and
maybe
we can see whats going on
--
-iwdu15
