On Sun, 17 Feb 2008 11:28:10 -0800, K Viltersten <tmp1@viltersten.com>
[quoted text, click to view]

Okay, that makes sense. I haven't used ProgressBar enough to know the
specifics, but from your description it seems reasonable to believe that
it animates between settings. I'd never noticed that before, even when
the value changes dramatically, but I may just not have been paying
attention.

I don't know if there's a way to bypass the behavior. I can think of an
ugly hack though: create a different progress bar, already set to the
maximum value, that remains hidden until the end. Then when you reach the
end, swap it for the "live" one. :)

Personally, I'd live with the animation. But I know how it can feel
sometimes when the GUI just isn't doing _exactly_ what you want it to.

[quoted text, click to view]

Okay. That's why I wrote "likely" as opposed to "must be". :)

[quoted text, click to view]

The minimal VS Designer template is generally Program.cs, Form1.cs, and
Form1.Designer.cs, yes. In the simplest cases, sometimes you can post
only the code in Form1.cs, as long as everything else is obvious. This is
in fact worth a first try, usually, since it produces the least amount of
posted code.

But yes, if you want people to be able to actually execute the same exact
code you're executing and thus help you work through what's going on, you
need to post everything.

Note that you can take those three files and merge them into a single one
(editing to remove extra "using" namespace declarations and breaks between
the "partial" Form1 class, of course, so that it call compiles). A person
won't be able to modify something like that in the designer, but it's
easier to get it up and working to start with and otherwise is just as
helpful.

On Sun, 17 Feb 2008 11:16:15 -0800, K Viltersten <tmp1@viltersten.com> =

[quoted text, click to view]
t.

What property are you referring to? If you're talking about the =

ProgressBar.MarqueeAnimationSpeed property, I believe that applies only =
to =

the marquee-style progress bar. That is, the one that just has the bloc=
ks =

animating across the bar over and over, rather than reflecting actual =

progress.

[quoted text, click to view]

I don't think that property would be useful in this case at all. But yo=
u =

could try it and see. I would try setting it to 0; if it has any effect=
=

on a non-marquee progress bar, maybe that would make the animation go aw=
ay =

entirely.

But again, from the docs anyway, it doesn't look like that'd actually ha=
ve =

any effect for a non-marquee progress bar.

[quoted text, click to view]

Instead of blocking your thread with the Sleep() method, you could =

(should, IMHO) instead use a timer or background thread. For example:

System.Windows.Forms.Timer timer =3D new System.Windows.Forms.Timer=
();

timer.Interval =3D 1000;
timer.Tick +=3D delegate(object sender, EventArgs e) { status.Text =
=3D =

"Done"; timer.Stop(); };
timer.Start();

Or:

BackgroundWorker bw =3D new BackgroundWorker();

bw.DoWork +=3D delegate(object sender, DoWorkEventArgs e) =

{ Thread.Sleep(1000); };
bw.RunWorkerCompleted +=3D delegate(object sender, =

RunWorkerCompletedEventArgs e) { status.Text =3D "Done"; }
bw.RunWorkerAsync();

I don't really recommend the latter, as I think it's not a great idea to=
=

block arbitrarily in thread pool threads (and should be avoided in any =

thread, for that matter). I also think the latter isn't quite as nice =

just in terms of how it's put together.

But with the delay only being 1 second, it's probably not that big of a =
=

problem if you really really wanted to.

I'd use the Timer solution though.

Either of the solutions would allow the text to not be updated until =

later, while still allowing the progress bar to do the animation it want=
s =

to do.

[quoted text, click to view]
, =

[quoted text, click to view]

No, not too much. I think that given that the bar animates, it would be=
=

nice to either have control over the animation, or to be able to receive=
=

updates regarding the status of the animation.

But as far as I know, neither of those are options. So if you really =

don't want the text updated until the progress bar has had a chance to =

visually reach the end, you're stuck with hacks such as the above. If =

you're going to do a hack though, at least try to make it as friendly as=
=

possible. Blocking the GUI thread for a full second isn't very friendly=
..

[quoted text, click to view]

I noticed that there's a property for the bar stating what time
it should take for the animation to move the fill to the
requested spot. I'm guessing that's the time i should delay
my text updating by. Correct?

When you mentioned a delay - is there an other way to do
it than threads? I've found this solution.

else {
System.Threading.Thread.Sleep (1000);
status.Text = "Done."; }

The thing is that while it postpones the text update (good,
good) it also removes the animation of the bar. By other
words - the bar waits for a second, then skips to the new
position, instead of being "pumped-up".

Most of all, it would be nice to get a report from the bar
saying "yey, i'm done animating" and then proceede.
Too much?

--
Regards
Konrad Viltersten
--------------------------------
IT-Consultant
Mandator, Fujitsu Services
0730 - 700 418

[quoted text, click to view]

Yes. My bad. I'm referring to a green bar at the bottom of the
screen, right on an instance of the ToolsStrip class.

[quoted text, click to view]

After an investigation i learned that the animated move of the bar
starts and WHILE it's being "pumped-up", (in its own thread, i'd
guess), the program continues updating the label. So, odd - no.
But sure ugly and inconvienient...

[quoted text, click to view]

I've tested creating a new, standard project with only this bar
being "pumped-up" as a single button is being pressed. Not
much of other code to interviene there.

[quoted text, click to view]

You surely don't refer to all the code being created, do you? VS
created at least three files for me, this far, i think. Did i
misunderstand something?

--
Regards
Konrad Viltersten
--------------------------------
sleep - a substitute for coffee for the poor
ambition - lack of sense to be lazy