MacOS SDL

SDL Development
1

Hello,
I’v installed the last SDL with the jlast extiention in the system
folder but:

I don’t understand why, about half of time,
when I hit a key, it does not stop to be considered as pressed.

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I have tried aggain and aggain to find a way to do it every time,
but I faild. It only ocures at random. It strangely dissapear if
I change the extention “SDL” with a new one, which is suposed to be the
same…

Thanks

Luc-Olivier

2

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I’ve heard of this, but I’m not sure why this would be. Perhaps the
SDL keyboard code should look at the low memory scancodes directly?

I have tried aggain and aggain to find a way to do it every time,
but I faild. It only ocures at random. It strangely dissapear if
I change the extention “SDL” with a new one, which is suposed to be the
same…

What do you mean?

See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software

3

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I’ve heard of this, but I’m not sure why this would be. Perhaps the
SDL keyboard code should look at the low memory scancodes directly?

I only seem to have the problem when running my program from the debugger
(in CodeWarrior).

4

At 8:56 AM -0700 2000.08.03, Sam Lantinga wrote:

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I’ve heard of this, but I’m not sure why this would be. Perhaps the
SDL keyboard code should look at the low memory scancodes directly?

This is probably not a good idea, as international keyboards

have different scan codes…

Since i'm a Mac developer whose just dropped in here (Howdy

everybody!), if you could describe your setup of the problem, maybe i
could take a look at it…–
::gLENN

-==-=+=-==-=+=-=*=-=±
Empty vastness
You can’t hear a sound
In space they float
Users unbound
-Front Line Assembly

5

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I’ve heard of this, but I’m not sure why this would be. Perhaps the
SDL keyboard code should look at the low memory scancodes directly?

I only seem to have the problem when running my program from the debugger
(in CodeWarrior).

I’ve seen it there too. Never tried it outside CW though.

Who did the event-handling stuff anyway? He/She/They can probably
comment better on the problem. I’ve never looked at it, but assumedly,
it’s catching the keydown event but missing the keyup event (assuming
that’s sent-- I seem to recall there was something odd about
keyup/keydown events, but can’t recall any specifics).

-Roy

6

For instance, if I want to write “hello”, I start pressing “h”,
but it gets "hhhhhhhhhhhhh…

I’ve heard of this, but I’m not sure why this would be. Perhaps the
SDL keyboard code should look at the low memory scancodes directly?

I only seem to have the problem when running my program from the debugger
(in CodeWarrior).

I’ve seen it there too. Never tried it outside CW though.

Who did the event-handling stuff anyway? He/She/They can probably
comment better on the problem. I’ve never looked at it, but assumedly,
it’s catching the keydown event but missing the keyup event (assuming
that’s sent-- I seem to recall there was something odd about
keyup/keydown events, but can’t recall any specifics).

I remember what the problem was. CodeWarrior switches the foreground
process context when it stops the running program, so it gets the key
up events. Supposedly the code is fine outside of the debugger. What
SDL should do is reset the keyboard when it loses focus. Could someone
with the problem watch the OS events that the program receives, and see
if there’s a good place to insert that code?

See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software