Quote:Original post by Anonymous Poster

Quote:Original post by EvilKnuckles666
hmm... would i be able to just have something that looks like this?

*** Source Snippet Removed ***

also:
so the pollevent() needs to be at the top with the getkeystate() and the pumpevents() needs to be at the bottom once i'm done checking the states and whatnot?

edit:
since the SDL_EVENT only checks one key, and i'm going to use the getkeystate() anyway? could i just avoid using pollevent() completely? or would i have to do just what i'm doing in that code i posted and just ahve a call to it?

Basicly, yes, you can have code like that. Take this as a note though, it DOESN'T have to look like that, it's just how I wrote some code. What you should do is:
*** Source Snippet Removed ***
My previous code was just an example.

No, it doesn't have to be in that order. It's just the order that I and many others prefer because of it's readability.

SDL_Event will hold events. Each key press, and any other message is an event. However, when you press 'w' and key holding it and press 'd' you will get a message for 'd', and not for 'w'. This is not what you wan't in games because your character then won't be able to move diagnoally. However, this is good for menus. This is where SDL_GetKeyState is nice. It get's a snapshot of the keys. So it can capture many keys at once. This way, you can have diagnol movement.

C++

Quote:Original post by Drew_Benton
I may be mistaken, but won't the line:

static unsigned char *s_Keys = SDL_GetKeyState(NULL);

Only call SDL_GetKeyState(NULL); once when that variable is first initialized first time around? Each subsequent call will not update the keystate since it's declared as static?

Of course, I go about all this input stuff a lot different from the ideas presented here, so rather than just post that, you can take a look at what I do if you want (lots of comments): Input Demo

// if in a function// notstatic unsigned char s_Keys = SDL_GetKeyState(NULL);//butstatuc unsigned char s_Keys;s_Keys = SDL_GetKeyState(NULL);

Quote:Original post by rip-off

Quote:Original post by Anonymous Poster
It's just that I had keys in my functions, but not static, and since in the example I made a Run() function that ran the keys I decided to make it static, off-my-head. Atleast it's only an example... Since I got... anonymous I can't edit things so I'll just say it here:
*** Source Snippet Removed ***

Good luck!

C++

your use of statics is unnessecary and adds nothing but possible confusion and bugs.

only consider statics when you need to retain data across function calls, which for c++ means making an object usually.

the lowdown on SDL events:

you _must_ call SDL_PollEvent(...) to clear the event queue. your application will not run correctly on some systems without periodically running pollevent.

calls to GetKeyState and GetMouseState are just handy ways of accessing an input device. you can get exactly the same information from polling events.

problems can occur when detecting mulitiple keypresses. basically, sometimes if you hold down 2 or 3 keys, no program can detect them, (on windows) you can try this out in notepad. try pressing p, then y then t then r without releasing any of them.

on my system, you cant simultaneously detect all of them. your application will get the same data then using Poll()ing or Get*State()ing...