All Keys Down

[kramlack]

Hi, I have a two part question.

The first is, is there a command for having all keys down, for example, " Key.isDown('all keys command')". The reason is, I'm trying to make a command for 'if all the keys AREN'T down'. This may seem stupid, but the reason for this is because I want my HERO MC to play the stand animation (frame one inside the MC) if none of the keys are down, but for some reason, the way I have it set up doesn't seem to work, the code right now, is as follows:

onClipEvent(enterFrame) {
gotoAndStop(1);
if(Key.isDown(Key.RIGHT)) {
_x += 5;
gotoAndStop(2);
}
if(Key.isDown(Key.LEFT)) {
_x -= 5;
gotoAndStop(2);
}
}

He plays the stand when not moving, but, when he does move, for some reason it only plays the first frame of the walk animation. Lately, I've been trying a new way of coding more professionally than I used to, so this has been a great bother to me, especially when I feel the answer should be so simple to figure out.

Finally, I'd like to reiterate my question, can someone tell me if there's a command for all keys, or better yet, an easy method of fixing this problem. Any help is greatly appreciated!

[EvanHayes]

hmm ive never tried this,you can use a loops to cycle through all the key codes.
try:

for(i=8;i<=191;i++){
if(!Key.isDown(i)){
trace("No keys are down")
}
}

that should work fine

[EvanHayes]

fuck i need to read in further nextime, instead of 2 ifs, use an if and and else if and an else for the standing animation,use the help files.

[zuperxtreme]

if(this key is down){
//do this
}else if(this other key is down){
//do this
}else{
//do this if the previous two aren't met
}

[korded]

Maybe I'm just out of it right now, but I think at least one big problem there is you have your key checks all within the onEnterFrame handler.. as well as the line of code before them saying to go to frame 1. So, every time a frame is played, the timeline is sent to frame 1, and then if one of the keys is down, is sent to frame 2.. but then back to frame 1 again right after, then frame 2, and so on.

Add the else { gotoAndStop(1) like the guy above said instead.

[EvanHayes]

At 1/2/09 09:55 PM, korded wrote: Maybe I'm just out of it right now

yup,must be. crack is whack.

think about it.

[kramlack]

At 1/2/09 09:55 PM, korded wrote: Maybe I'm just out of it right now, but I think at least one big problem there is you have your key checks all within the onEnterFrame handler.. as well as the line of code before them saying to go to frame 1. So, every time a frame is played, the timeline is sent to frame 1, and then if one of the keys is down, is sent to frame 2.. but then back to frame 1 again right after, then frame 2, and so on.

Add the else { gotoAndStop(1) like the guy above said instead.

I'd like to, since that was my old method of programming, but I always assumed it was an 'incorrect' method, continually using else if statements for something as simple as key presses. Is there no other way around it?

[korded]

I don't think it's that big a deal when used on such a small scale as what you've shown above.. the only real problem with it was it was constantly setting your timeline to the first frame, then toggling between the first and second frame really fast when you have a key down.

...but yes, in the case of key pressed at least, there is an alternative fortunately. Check out listeners. You'll have to look them up (actionscript dictionary?) for real understanding, but here's an example.

keytracker = new Object();

keytracker.onKeyDown = function() {
	if (Key.getCode() == 65) {
		trace("you are pressing down A");
	} else if (Key.getCode() == 68){
                trace("you are pressing down D");
       }
}

keytracker.onKeyUp = function() {
	if (Key.getCode() == 65) {
		trace("you have released A");
	} else if (Key.getCode() == 68) {
		trace("you have released D");
	}
}

Key.addListener(keytracker);

[korded]

One point I should mention actually is that using the above method, your script isn't constantly checking for a condition; the listener will perform the specified actions one time upon your trigger.. which in the above case is the pressing and releasing of the A and D keys.

Someone more experienced can correct me if I'm off on something here.

[kramlack]

Thanks, sounds fairly understandable. I'll make sure to look into listeners for further explanation.

[faxmunky]

onClipEvent(key.UP){}

I think that's right... not sure though