[Gambas-user] WAIT ... is it an (un) necessary evil for my app?

[Jussi Lahtinen]

I had similar problems, but I had only minor performance penalty. So
in my case WAIT was ok.
So I don't think I can help but...
Hard to believe that progressbar really needs 0.25s to just refresh...
WAIT must be doing something else too.
In documentation of refresh, there reads:
"If you need an immediate refresh, call WAIT after having used this method."

pbprog.Refresh()
WAIT
Should do it, but I'm sure you already tried that. Bug..?
If not, maybe there should be method RefreshNow, which waits until
refresh is done and after that continues execution.
Or more generally;
pbprog.Refresh() WAIT
like with EXEC instruction.

To wishlist? Better ideas?

Regards,
Jussi


On Wed, May 27, 2009 at 18:31, M0E Lnx <m0e.lnx at ...626...> wrote:
> Anyone else have any other suggestions?
>
> I still can't get this to work.
> Adding the wait on the process_kill() event also allows the
> progressbar to refresh, but I the results are the same...performance
> suffers with this lag at the end of every process.
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user
>