the keyboard/thread handling in SDL is such that if I am debugging in
gdb, or even if my program cores at an inopportune time, I lose
keyboard auto-repeat…which is a BIG pain in the ass in emacs :>
any nice solution around this ?
j–
/* ------------------------------------------------ *
Always remember you’re unique, just like everyone else
* ------------------------------------------------ */
A shell scrip wrapper around xset should do it. (Is xset the right program?? I
forget :)On Mon, Aug 03, 1998 at 05:26:25PM -0700, Jeff wrote:
the keyboard/thread handling in SDL is such that if I am debugging in
gdb, or even if my program cores at an inopportune time, I lose
keyboard auto-repeat…which is a BIG pain in the ass in emacs :>any nice solution around this ?
–
– Michael Samuel
Don’t trust anything I say, just give it consideration.
the keyboard/thread handling in SDL is such that if I am debugging in
gdb, or even if my program cores at an inopportune time, I lose
keyboard auto-repeat…which is a BIG pain in the ass in emacs :>
any nice solution around this ?
The latest version of SDL in CVS has a feature that will perform
graceful cleanup when it crashes.
I agree though, it’s annoying to have key repeat turned off in gdb.
In normal operation when the mouse leaves the window key repeat is turned
back on, but if you’re single stepping through code, that of course won’t
happen. If you want to turn it off, Just comment the XAutoRepeatOff()
call in SDL_sysvideo.c and SDL_sysevents.c
Sam Lantinga writes:
the keyboard/thread handling in SDL is such that if I am debugging in
gdb, or even if my program cores at an inopportune time, I lose
keyboard auto-repeat…which is a BIG pain in the ass in emacs :>any nice solution around this ?
The latest version of SDL in CVS has a feature that will perform
graceful cleanup when it crashes.I agree though, it’s annoying to have key repeat turned off in gdb.
In normal operation when the mouse leaves the window key repeat is turned
back on, but if you’re single stepping through code, that of course won’t
happen. If you want to turn it off, Just comment the XAutoRepeatOff()
call in SDL_sysvideo.c and SDL_sysevents.c
thanks for the prompt respons Sam…on another note:
my cvs update all of a sudden broke for SDL (note it works for
everything else i currently remotely update from)…
pc-4374:~/projects/sdl> cvs update
? SDL/lib/libSDLx11.so.0.7
? SDL/obj/Makefile
? SDL/obj/x11
? SDL-demos/aliens/SDL_path_OK
? SDL-demos/aliens/aliens
? SDL-demos/fire/SDL_path_OK
? SDL-demos/fire/fire
? SDL-demos/stars/SDL_path_OK
? SDL-demos/stars/stars
? SDL-demos/warp/SDL_path_OK
? SDL-demos/warp/warp
cvs server: Updating .
cvs server: failed to create lock directory in repository /home/slouken/cvsroot': Permission denied cvs server: failed to obtain dir lock in repository/home/slouken/cvsroot’
cvs [server aborted]: read lock failed - giving up
is this my fault? im a relatively novice user of CVS
j
my cvs update all of a sudden broke for SDL (note it works for
everything else i currently remotely update from)…
Try it now.
is this my fault? im a relatively novice user of CVS
So am I 
I realize this is probably not the best place to be asking this, but
I’ve noticed that traffic has slacked off, and I’ve now got too much
time on my hands.
Anyway, I was wondering if there were any plans on porting SDL to
SVGAlib, or if SVGAlib is officially dead (Though they released v 1.3.0
a little while ago, I’m told)–
| |/ | | | _ | | | mailto:@Knight_Walker |
| / | / / | | http://www.aros.net/~kwalker |
| \ | ___ | | |
| |\ | | / \ | | The Kobran Imperium (801)265-1299 |
|| || || || _____________________________________/
Anyway, I was wondering if there were any plans on porting SDL to
SVGAlib, or if SVGAlib is officially dead (Though they released v 1.3.0
a little while ago, I’m told)
My long-term memory is a little-bit hazy, but I remember that a few months ago
there was SVGALib support in SDL. It never worked for me (SVGALib, not SDL :-),
so I don’t know whether it was a “I’ll implement it later” hook, or actual
support.
Anyway, SVGALib is dead - My ET6000 doesn’t work with it 
(Yes, one of the boards that had open specs released before any cards used it!)On Tue, Aug 04, 1998 at 07:04:42AM -0600, kwalker at aros.net wrote:
–
– Michael Samuel
Don’t trust anything I say, just give it consideration.
My long-term memory is a little-bit hazy, but I remember that a few
months ago there was SVGALib support in SDL. It never worked for me
(SVGALib, not SDL :-), so I don’t know whether it was a “I’ll implement
it later” hook, or actual support.
Well, the reason I ask is because as of SVGAlib 1.2.13, my Trident TGUI
9680 card is supported. That’s the one in my main Quakestation–er! I
mean workstation. I’m thinking of hunting down 1.3.0 (If I can find it)
and see what they upgraded/fixed. I like SVGAlib because it is
CONSIDERABLY faster than X (Although my only real benchmark is Quake2).
I’d like to see if DGA can bring X up closer to the performance of
SVGAlib, but I don’t know enough about SVGAlib to write any benchmarking
stuff in it.
Anyway, SVGALib is dead - My ET6000 doesn’t work with it
(Yes, one of the boards that had open specs released before any cards
used it!)
As I recall, some ET cards have been weird in SVGAlib (Which is why they
have their own config file and bug work around .txt file). Have you
looked at 1.3.0? It might work with your ET6000.
-KW
Anyway, I was wondering if there were any plans on porting SDL to
SVGAlib, or if SVGAlib is officially dead (Though they released v 1.3.0
a little while ago, I’m told)
SVGAlib is officially dead. 
Actually, it doesn’t work on any of the
systems I have access to, but more than that, it only works with a handfull
of cards. I chose DGA over SVGAlib because it’s more widespread.
If anyone wants to add SVGAlib drivers, go ahead, but I probably won’t.
My long-term memory is a little-bit hazy, but I remember that a few months ago
there was SVGALib support in SDL. It never worked for me (SVGALib, not SDL :-),
so I don’t know whether it was a “I’ll implement it later” hook, or actual
support.
It was an “I’ll implement it later” hook. I actually plan to implement a GGI
driver, which should come out in a few weeks/couple of months.
I’ve also been toying with the Mac, since I now have access to Codewarrior
and a decently fast PPC.