User presses and holds the primary fire button:
activated gets called for mode 0
fire loops using mode 0
User still holds the primary fire button, but also presses the secondary fire button and holds it:
deactivated gets called for mode 0
activated gets called for mode 1
fire loops using mode 1
.
.
.

I'd like to remove this interference, so that no code is handled for the secondary fire button, when the primary one is still held. But it does not seem to be possible.
Any ideas?


------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)

Just run the same code for bolth modes.

Ok, my explanation might have been a bit poor, so sorry. I, of course, want to have different firemodes, but they should not mess with each other, as they do in standard LEC cogs. I'm not sure if that's possible, because it seems to ignore any breakout statements I made...

------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)

So you want both fire modes possible at the same time?

OR

You want Fire1 to not get interuppted if Fire2 is pressed? This is impossible, unfourtunatly. Deactivated will always get called if one fire mode is "active" and the other one is activated.

------------------
-Hell Raiser
Without struggles there is no progress
DBZ: The Destruction is Real

Yeah, that's what I was expecting. **** it. Anyway, thanks.

------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)

Why not just put a relational test and tell it to disregard activated, fire, and deactivated messages is a value is set. That may not technically negate those messages, but it would effectively. Or I should think it would.

That's what I'm doing, but it's not working, because firemode 1 gets deactivated upon activation of firemode 2 no matter what the code is.

------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)