Simple Workaround?

[MajorityCA]

I haven't been to these forums in ages! Wow.

Anyways, I'm wondering how to fix an issue. I'll describe it in as general of terms as I can.

Say you have these events,

"If you press Z while M=0, then do X, and set M to 1."
"If you press Z while M=1, then do Y, and set M back to 0."

Seemed simple to me, but I've come across an issue. My guess is that MMF2 runs this too fast, and when you press Z nothing happens because it goes through both events so quickly. I've had this issue before, but it's been so long that I can't remember how I worked around it. How do you guys do this?

Sorry for my bad memory.

[mojofltr]

There are probably many ways, but I would add a flag into the mix:

Upon pressing "Z"
Alterable Value M=0
Internal Flag 0 is off
	Do X
	Set Alterable Value M to 1
	Set internal flag 0 on

Upon pressing "Z"
Alterable Value M=1
Internal Flag 0 is off
	Do Y
	Set Alterable Value M to 0
	Set internal flag 0 on

(DO NOT) Repeat while "Z" is pressed
	Set internal flag 0 off

[MajorityCA]

Hmm... that didn't seem to work. I tried using the flag only (the variable's only there to determine what the button does), and using a flag and the variable, and got no results with either of them. :/ Any suggestions?

[LB]

You've run into the trap that many others have run into.
See the first two posts here:
http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=176557

The issue is not that the events run too fast, but that both events run within the same frame.

[mojofltr]

I'm not exactly sure what you're trying to perform... so this may or may not suit your program:

http://mfa.aquadasoft.com/upload/1312938602-Hi.mfa

The first frame is identical to the code I posted above. Since you said you didn't really need the alterable value, I added a second frame that uses a single flag to perform the same thing. It would work without the "only one action when event loops" conditions, but I put that in there so that pushing the "z" button results in only one action each time. (In this example, it wouldn't really matter - there would be no difference to continually set the active object to invisible. However, if you were wanting to, say, add 500 to a value... then without the "only one action when event loops" condition, it would continue to add 500 as long as the flag was set.)

Okay, I hope that made sense.

[MajorityCA]

Yay! I figured that it was common because it's so simple, but your posts and example helped me remedy it. Thank you LB! It is much appreciated.

Edit: Didn't see that you posted mojofltr. It's all solved now, but thank you for your help as well.