ProgressBar not updating until end of loop?

[Nudgy]

Hi all,

In a simple loop I am going through all the lines of a List and setting a ProgressBar accordingly. However, the progress bar does not actually change to 100% before the loop finishes entirely. I checked the documentation and forum, but didn't manage to find anything clearly relevant. My guess is that the loop is blocking the progress bar from updating (maybe some kind of threading or DoEvents equivalent is needed?).

For this project, I am using Linux - in case that makes a difference.

Any suggestions?

Thanks.

[jacdelad]

Is your event loop working while your progress stuff happens?

[Axolotl]

pretty sure, that jacdelad leads you to solve your problem.

Otherwise: Any code?

[Nudgy]

Is your event loop working while your progress stuff happens?

I haven't touched the event loop for the purpose of the "List loop".

In simplified psuedo-code I am just doing more or less the following:

Code: Select all

Procedure x()

      SetGadgetAttribute(#ProgressBarID, #PB_ProgressBar_Minimum, 0)
      SetGadgetAttribute(#ProgressBarID, #PB_ProgressBar_Maximum, NumberOfTotalLinesInList)

     ForEach sourceList()

           SetGadgetState(#ProgressBarID, IncrementedNumberForEachLoop)

          ; Do some stuff with the List here (incuding adding lines to a ListIcon)
     Next

EndProcedure

[jacdelad]

When the function is called, the event loop waits until the function is done. No event processing -> no redrawing. Create a thread to process your stuff.

[Fred]

And if you really don't want to a thread, you can put 'while windowevent() : wend' at regular interval to flush the events.

[jacdelad]

...but be aware that this way all events die painfully without being processed!

[Nudgy]

And if you really don't want to a thread, you can put 'while windowevent() : wend' at regular interval to flush the events.

Thanks, Fred. This was actually the first thing I tried, with inspiration from the forum. But it returned the error "[ERROR] WindowEvent(): WindowEvent() and WaitWindowEvent() can not be called from a 'binded' event callback." Unfortunately, I am not smart enough to figure out what that error means I guess it might be caused by the use of BindEvents elsewhere in the code somehow. If you have any hints in that regard, it would be much appreciated.

Otherwise, this might be a good opportunity for me to learn about threading

[jacdelad]

It means exactly what it says: You used Bind...() to let the procedure be automatically called. Procedures called by that are not allowed to use WaitWindowEvent(), because this could cause a fatal sprial of events calling the procedure over and over, stacking it into infinty.

[DarkDragon]

...but be aware that this way all events die painfully without being processed!

And you can slow down the process by sending events by e.g. moving your mouse.