I think I figured out the slight hesitation on the little testsprite
program (which part of my explorative app is based on) - when the
program starts up, the files stdout and stderr are created in the
directory and that coincides with the slight hickups. The files are
empty - it seems that even though printf isn’t being called, the files
are formed anyway. Any way around this? Or do I just do something
non-animated for a moment to cover up the hickup?
Michael Vanecek wrote:> I re-initialized the disk on the Rev-C iMac, upgraded to MacOS 9.0 and
reinstalled everything and went into SDL-devel and the test progs
compiled with nary a problem. I can’t say whether it was a problem with
the old MacOS 8.5, or whatever the previous owner had done to it. I plan
on upgrading the RAM to 512Mb (from 96 now) and the harddrive to a 40 or
60 Gb and drool over all the neat SDL stuff on Mac.
One Q - the testsprite application has a slight hickup just as it starts
up before resuming animation - it starts, stops briefly and then
continues. An app I’ve been putting together to teach myself SDL (using
some of this and some of that) also does the same thing. I’m using the
basic SDL_Getticks() function on my learning application. Could the Mac
be hesitating to do the math once it all starts, or is there something
else I should be aware of (Mac quirks like Endian stuff or math stuff?).
Another possibility is that it takes an extra moment to load the event
functions which are after all the images and animations are loaded…
http://dotfile.net/ - Dedicated to Open Source Software