Fix for a couple of issues in r243.
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.