Fix for a couple of issues in r243.
Did the recent updates (from early this year) change anything about the For loop logic?
Cause some of them in my old projects that involved the (wait loopindex * x seconds) broke after reopening. Already fixed it (because technically the logic is more "correct" now, since recalling the current loop index after waiting it to be complete should return nothing, since the loop already ended after the "wait" time). Just curious about it
It's difficult to comment - we've made loads of changes. We strive to keep all projects backwards-compatible, but sometimes bug fixes or other intentional changes can affect how projects work. The best way to check if something has changed your project is test it in older releases and find which release made the change.
hmmm, understood. Not a complaint tho. The new logic seems to be more correct (since the loop should technically only lasts for like 1 tick or something; so the "loopindex" variable should indeed not be recallable past that).
Actually tried to test it on some older releases but I've had already saved it in a recent one (so couldn't 'reverse' it back... I know I can edit the file, but that usually breaks something). Although it worked correctly in a build (exported) from some months ago.
Just found it strange that I (afaik) didn't find it in any of the recent changelogs. Maybe it (if can be confirmed) should be mentioned somewhere, to warn old users about the quite major change in the engine's logic (for loops in general).
It may well have been mentioned in the release notes. But from what you've said I'm afraid it's difficult to identify any specific release. Testing your project regularly in the latest C3 release would also help identify specific releases when things change. The longer you leave it, the harder it is to work out what happened.
the workaround I found was to create a local number and set it (before the "wait" event) to the current loopindex. So it can be recalled later as the 'old' loop index.
not asking for it to be "fixed" tho. Just curious if u knew/remembered changing some aspect about it. Seems like it might have been some time tho (didn't work on my project for the last 2-3 months, to that explains).
Don't know about the practicality of it, but maybe construct could have some (IDE-like) notifications on events/expressions that had their logic messed with (such as the OR modifier, some time ago). Much like the 'deprecated' terms on languages in general.