hi,
are there any known issues with running an SDL 1.2.7 app in full
screen under OSX (10.3.4)?
I do this:
// … from Video_Init:
int video_flags = SDL_HWSURFACE | SDL_DOUBLEBUF | SDL_FULLSCREEN;
int width = 480, height = 320, depth = 32;
This is kind of irrelevant, but, I might as well put it out there.
Every tutorial on the internet uses code like this. They put together
the video flags and store it in a variable. But they never use this
information afterwards, and my guess is that you aren’t either. You
don’t NEED to store your video flags in a variable before calling
SDL_SetDisplayMode().
…um, I don’t know if 320x480 is a valid fullscreen display
dimension: try 640x480
Closer would be 480 x 360, that is the lowest most VGA monitors support.
…also remember you don’t need double buffering in OSX; the window
manager does that for you!
-
I doubt Jay is only developing his application for only OS X,
otherwise, why use SDL at all… if you want double buffering, ASK FOR
DOUBLE BUFFERING. This was BAD advice.
-
The Window Composition Layer (Quartz Extreme) is responsible for
window drawing. This is not the responsibility of the window manager
(though they obviously work closely together, they are not the same
component.)
-
OSX will not ALWAYS buffer your application’s display the way you’re
suggesting. Yes it’s true, that the window composition layer (not the
window manager) does create the image of your window off-screen and in
that sense there is a second display buffer, but without actually
requesting double buffering, there are two possible behaviors for the
window composition layer:
a) composition that is asynchronous with your application
b) you get real hardware access to the portion of the screen occupied
by your window, no buffering at all
In Jaguar I’ve been told you get B. I use panther, and I get A.
Other than that, I’d look at the error messages that are produced,
they often provide vital clues 
Jay, did you get any error messages? You should check for that kind of
early on, so I assume that you didn’t get any, since you didn’t mention
any in your email.
l8r,
jamie
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
Jay, I’ve never had any problem, I was going to suggest you do one of
the following, but decided to postpone my suggestion until other people
had a chance to say something, in case there actually were any
"gotchas."
-
Post all your source code, you may have a fairly coding mistake that
will be found quickly by an objective reader.
-
Test your code on another OS, perhaps it’s not an OS X problem at
all.
-
Test an application that does what YOU are trying to do, and see if
it has a problem on your system. If it doesn’t, again, you may have
made a simple mistake in your code.On Jul 16, 2004, at 12:42 PM, James Tittle II wrote:
On Jul 16, 2004, at 5:30 AM, Jay Vaughan wrote: