Hi,
is there some support in SDL to read out several
USB joysticks that are all connected at the same
time?
If not, is there something like this planned?
Is there support for this “vibration” that is activated
when a monster hits you really hard or you drive a
car against the wall?
Is there some example code available?
Best regards,
Torsten.
is there some support in SDL to read out several
USB joysticks that are all connected at the same
time?
There must be, as the SDL joystick code in xmame allows the use of two USB
joypads.
Is there some example code available?
Heh, I could point you to the xmame codebase, but I’m sure there are people on
this list that have something a tad smaller readily available. 
Regards,
Pieter Hulshoff
Hi All 
Can anyone recommend me a good free bug tracer type program that works with
SDL apps?
What I’m looking for is something that might report memory leaks, array
overruns and other little bits and pieces so I can see if I’ve done (hmmm…
quite possibly) anything really silly in Metal Blob Solid.
Anyone know of anything that might be useful?
Cheers,
Stevie
Stephen Sweeney wrote:
Can anyone recommend me a good free bug tracer type program that works with
SDL apps?
For what OS?–
Milan Babuskov
http://njam.sourceforge.net
Oops! Sorry… Linux! :)On Saturday 13 Dec 2003 10:02, Milan Babuskov wrote:
Can anyone recommend me a good free bug tracer type program that works
with SDL apps?For what OS?
MSS - Memory Supervision System
http://hem1.passagen.se/blizzar/mss
Cross-platform, GPL, and works well.
HTH,
JPOn Saturday 13 December 2003 01:39 am, Stephen Sweeney wrote:
Can anyone recommend me a good free bug tracer type program that works with
SDL apps?What I’m looking for is something that might report memory leaks, array
overruns and other little bits and pieces so I can see if I’ve done
(hmmm… quite possibly) anything really silly in Metal Blob Solid.Anyone know of anything that might be useful?
is there some support in SDL to read out several
USB joysticks that are all connected at the same
time?
Yes. You can get a list of all attached joysticks (USB or otherwise),
and their attributes, and use the ones you please. Check the docs for
specifics.
–ryan.
http://valgrind.kde.org/
Fortunately, it’s not a KDE program 
Stephen Sweeney wrote:> On Saturday 13 Dec 2003 10:02, Milan Babuskov wrote:
Can anyone recommend me a good free bug tracer type program that works
with SDL apps?For what OS?
Oops! Sorry… Linux!
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
Remember, bug-tracking shouldn’t depend on the libraries you use – and I’ve
never seen one depending on a library. In all honesty, just use a bug
tracker you like, and go from there.
If you don’t yet have a favorite tracker you’re familiar with: Fenris is
pretty decent and free – http://www.lokigames.com/development/fenris.php3
From: bernhard.bliem@chello.at (Bernhard Bliem)
To:
Sent: Sunday, December 14, 2003 2:25 AM
Subject: Re: [SDL] Bug trackers / tracers?http://valgrind.kde.org/
Fortunately, it’s not a KDE programStephen Sweeney wrote:
On Saturday 13 Dec 2003 10:02, Milan Babuskov wrote:
Can anyone recommend me a good free bug tracer type program that works
with SDL apps?For what OS?
Oops! Sorry… Linux!
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.547 / Virus Database: 340 - Release Date: 12/2/2003
Thanks everyone
I’ve currently got a few probs like one of my project seg faulting so I’m
trying to find out why. I’ll look into all these recommendations and see what
comes up trumps
Ta,
Stevie
hey stephen,
you probly already know this technique but just in case (or for other people
listening) here it is anyways.
whenever my code has problems crashing, i use a log function to log info to
a file at regular intervals like this:
int main (void)
{
Log(“starting main”);
//some code here
Log(“did some code”);
//some other code here
Log(“did some other code”);
}
and then i run it and if it says “did some code” in the file but not “did
some other code”, i know the problem lies in that last block of code so then
i do the same thing as above but inside the function(s) in there. i keep
doing this, going deeper in until i find the line thats causing the problem
then have it output the values of variables to the log file to better
understand whats going on etc.
this technique has worked great for me every time in finding crashes. i
guess it wouldnt be real helpful in finding memory corruption or memory
leaks though.
anyways, hope it helps although you probly already tried this.> ----- Original Message -----
From: stephen.sweeney@parallelrealities.co.uk (Stephen Sweeney)
To:
Sent: Sunday, December 14, 2003 1:28 PM
Subject: Re: [SDL] Bug trackers / tracers?Thanks everyone
I’ve currently got a few probs like one of my project seg faulting so I’m
trying to find out why. I’ll look into all these recommendations and see
what
comes up trumpsTa,
Stevie
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
whenever my code has problems crashing, i use a log function to log info to
a file at regular intervals like this:int main (void)
{
Log(“starting main”);
Make sure your Log function does a fflush() before returning, else not all
the log entries will be written if the program crashes.
i keep doing this, going deeper in until i find the line thats causing the
problem then have it output the values of variables to the log file to
better understand whats going on etc.
Do a binary search for the bug, rather than a linear search
this technique has worked great for me every time in finding crashes. i
guess it wouldnt be real helpful in finding memory corruption or memory
leaks though.
Yep, doesn’t do much for finding memory leaks (use wrappers for malloc() and
free() to check for leaks or corrupted pointers), but it does help greatly in
finding some types of crashes.
JPOn Sunday 14 December 2003 01:51 pm, Alan Wolfe wrote: