Two bugs

[Phi]

Bug 1 is an oddity.
The MFA is more detailed, but basically, switching sets of conditions around an OR changes whether it can be true or not. This occurs at edittime and runtime.
http://dark-wire.com/temp/Bug!%202.mfa

Bug 2 is only for people with access to edrt.exe's source code. For some reason MMF2 Dev crashes when I run edrt.exe, and here's a link to the memory dump. Visual Studio should be able to open it for debugging.
http://dark-wire.com/temp/edrt.rar
Opening a fresh instance of MMF2 Dev is fine, that one can run edrt.exe with the same MFA without issues, so something must have screwed up with the original MMF2 process.

[Francois]

OR problem : this cannot be corrected until MMF3.

In the first event group, when you press W, the very first Upon pressing condition is true. It sets a flag in the group of events so that it does not repeat the next time.
Then the next condition is false, so the other part of the OR is explored. The Upon key press condition tests the flag, as it is set, it returns false.

It works with "Q", as the first part of the event is true.

This kind of bugs happens as the event engine was not at start constructed to handle OR (or fast loops). It is not recursive, and the flags of the conditions are global to the event line.
In MMF3, I'll make it recursive (no more loop object selection problems), and use flags in the conditions instead of the event group.

[Phi]

Ah, that's a pain in the butt and a big glitch for sure. I can work around it though by using two events.
Any clues about the 2nd bug?

[Francois]

No, this is not enough for complex bugs. Can you send me your application?

[Phi]

Well, any application launched with that instance of MMF2 crashes in that manner. A fresh procesof MMF2 does not encounter the bug.

Opening a fresh instance of MMF2 Dev is fine, that one can run edrt.exe with the same MFA without issues, so something must have screwed up with the original MMF2 process.

So I can't trace it to an mfa, just a particular state MMF2 got in somehow which makes it run edrt.exe in an invalid manner with every mfa.
So I guess you can't trace this one?