Progress during a while.

So, using the trick from a for loop, I'd put a wait 0.1 in my while statement in order to update a progress bar. However, if you put a wait inside a while, the net results seems to be it locks up the entire app, which ends in an 'oh-snap' in the preview AND the editor.

Now surely, there must be some way of updating a progress in the midst of a while without locking everything up? From what I'm seeing, if you execute a while, everything freezes till it's done.

the wait doesn't slow down the execution of the eventsheet - it only defers the actions after the wait until the desired time. So, the while statement is still running 60 times a second...

instead of a while, I would probably use a global variable as a countdown - and every tick subtract dt from it, and update the progress as that goes down.

You need "Wait loopindex*0.016" if you want the loop to iterate 1 tick at a time. But this won't work with While loop, you should use Repeat or For:

Repeat 100 times
	Wait loopindex*0.016
	ProgressText append text "."
	// do some cpu-intensive stuff here, 1/100 portion of it.
	// For example, if you need to fill a million array records, fill 10000 here

Well if you're not worried about interrupting a loop with the 0.1, then you might as well just use ticks.

God, it's taken me 2 days to get this while to work. The thought of rewriting yet again it makes me ill. Plus, I'm going to have another much larger while loop that would be a bigger nightmare to convert into something else. Instead of completely rewriting this code into a different type of loop, is there no way to update a progress? It just seems bizarre to me that a while loop should completely freeze the app till it's done with no way to update a text or a progress bar.

For long loops with progress indication, I use nested for loop with a progress/iteration counter.

Every tick if 0<"progress"<=100, add 1 to progress

> For "loop" from totaloperations/100*(progress-1) to totaloperations/100*progress

This will start running by setting progress to 1. 100 is an arbitrary number for how many steps/ticks you want to divide your operation for. My main application of this is for parsing, where totaloperations is the tokencount of what I want to parse.

Ahh, you can also do that with the method I mentioned above.

Split the loop into byte size chunks that runs every tick.

This could possibly be an interesting feature suggestion.

A stop loop action except that instead of terminating the loop, it will complete anything that remains in the following tick.

In Delphi there's a while and a repeat (and of course for loops) The difference between those is, in a while loop, if the condition is met anywhere in the middle, the loop breaks. In the repeat loop, it only checks at the end of the loop to see if the condition is met and then breaks.

But, that's just me being wishful. Considering the headache I've been through with that one above, it's obvious I still haven't figured out the logic of C3 loops.

You can still use while (stop loop still will work the same way), but you'll need to track your progress manually rather than using loopindex is all.

Of course. The problem is, while the loops is running there doesn't appear to be any way to update a progress bar, a text or anything else. One of my while loops could likely take up to 5 seconds, during which time, the game is completely frozen. Since this will be during startup, those kinds of delays are considered acceptable. Not updating a text or a progress to prove the game hasn't crashed for 5 seconds? The vast collection of impatient gamers on this planet will have a collective embolism.

I exaggerate but you get the point.