Mercurial > sdl-ios-xcode
view VisualC.html @ 983:7f08bd66f1ca
Date: Fri, 19 Nov 2004 06:23:53 -0800 (PST)
From: Eric Wing
Subject: OS X Mouse inversion problem fix (again)
Here's yet another patch for the OS X mouse inversion
problem. This should fix the problem once and for all.
I know I've said this before, but *This time for
sure!* :)
If you recall, my last patch broke the non-OpenGL
windowed code and caused the inversion to occur there
instead. Max submitted a patch that partially reverted
the changes back which included the os version hack
which is currently the most recent CVS.
Aaron Sullivan identified and reported to the mailing
list the other day, that the last partial regression
of the code broke OS X 10.2. Looking over the results,
I'm thinking that I was slightly more successful than
I thought at unifying the code. I think I was trying
to unify the code base for OpenGL and non-OpenGL
windowed modes for all versions of the OS. It looks
like I failed at at unifying the OpenGL and non-OpenGL
code, but I did succeed at unifying the OS versions.
Thus, we no longer need the hack for the OS version
checks. The partial regression still included an OS
check which is what broke things for < 10.3.
Attached is the patch for SDL_QuartzWM.m. It basically
is a half-line change that removes one of the two
checks that decides if the mouse coordinates need to
be inverted, i.e:
if (system_version >= 0x1030 &&
(SDL_VideoSurface->flags & SDL_OPENGL) )
becomes this:
if(SDL_VideoSurface->flags & SDL_OPENGL)
With Aaron's outstanding help, we have collectively
tested:
windowed OpenGL
windowed non-OpenGL
fullscreen OpenGL
fullscreen non-OpenGL
under OS X 10.2 (Jaguar), 10.3 (Panther), and 10.4
(Tiger).
We don't have access to 10.0 or 10.1, but since the
original problem didn't materialize until 10.3, I'm
hopeful that testing 10.2 is sufficient. And now that
the code is uniform, I'm also hoping we'll be safe
moving forward to deal with future revisions of the OS
with this issue.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sun, 21 Nov 2004 00:57:47 +0000 |
parents | 136d97397288 |
children | e044e7c70a50 |
line wrap: on
line source
<HTML> <HEAD> <TITLE>Using SDL with Microsoft Visual C++</TITLE> </HEAD> <BODY> <H1> Using SDL with Microsoft Visual C++ 5,6 and 7 </H1> <H3> by <A HREF="mailto:snowlion@sprynet.com">Lion Kimbro </A>and additions by <A HREF="mailto:james@conceptofzero.net"> James Turk</A> </H3> <p> You can either use the precompiled libraries from <A HREF="http://www.libsdl.org/download.php"> the SDL Download web site </A>, or you can build SDL yourself. </p> <H3> Building SDL </H3> <P> Unzip the <CODE>VisualC.zip</CODE> file into the directory that contains this file (<CODE>VisualC.html</CODE>). <STRONG><FONT color="#009900">If you are using Visual C++ 7 (.NET) you will need to use the file <code>VisualC7.zip.</code></FONT></STRONG> </P> <P> Be certain that you unzip the zip file for your compiler into <strong>this</strong> directory and not any other directory. If you are using WinZip, be careful to make sure that it extracts to <strong>this</strong> folder, because it's convenient feature of unzipping to a folder with the name of the file currently being unzipped will get you in trouble if you use it right now. And that's all I have to say about that. </P> <P> Now that it's unzipped, go into the VisualC <STRONG><FONT color="#009900">(VisualC7)</FONT></STRONG> directory that is created, and double-click on the VC++ file "<CODE>SDL.dsw</CODE>"<STRONG><FONT color="#009900"> ("<CODE>SDL.sln</CODE>").</FONT></STRONG> This should open up the IDE. </P> <P> You may be prompted at this point to upgrade the workspace, should you be using a more recent version of Visual C++. If so, allow the workspace to be upgraded. </P> <P> Build the <CODE>.dll</CODE> and <CODE>.lib</CODE> files. </P> <P> This is done by right clicking on each project in turn (Projects are listed in the Workspace panel in the FileView tab), and selecting "Build". </P> <P> You may get a few warnings, but you should not get any errors. You do have to have at least the DirectX 5 SDK installed, however. The latest version of DirectX can be downloaded or purchased on a cheap CD (my recommendation) from <A HREF="http://www.microsoft.com">Microsoft </A>. </P> <P> Later, we will refer to the following .lib and .dll files that have just been generated: </P> <ul> <li> SDL.dll</li> <li> SDL.lib</li> <li> SDLmain.lib</li> </ul> <P> Search for these using the Windows Find (Windows-F) utility, if you don't already know where they should be. For those of you with a clue, look inside the Debug or Release directories of the subdirectories of the Project folder. (It might be easier to just use Windows Find if this sounds confusing. And don't worry about needing a clue; we all need visits from the clue fairy frequently.) </P> <H3> Creating a Project with SDL </H3> <P> Create a project as a Win32 Application. </P> <P> Create a C++ file for your project. </P> <P> Set the C runtime to "Multi-threaded DLL" in the menu: <CODE>Project|Settings|C/C++ tab|Code Generation|Runtime Library </CODE>. </P> <P> Add the SDL <CODE>include</CODE> directory to your list of includes in the menu: <CODE>Project|Settings|C/C++ tab|Preprocessor|Additional include directories </CODE> . <br> <STRONG><FONT color="#009900">VC7 Specific: Instead of doing this I find it easier to add the include and library directories to the list that VC7 keeps. Do this by selecting Tools|Options|Projects|VC++ Directories and under the "Show Directories For:" dropbox select "Include Files", and click the "New Directory Icon" and add the [SDLROOT]\include directory (ex. If you installed to c:\SDL-1.2.5\ add c:\SDL-1.2.5\include). Proceed to change the dropbox selection to "Library Files" and add [SDLROOT]\lib.</FONT></STRONG> </P> <P> The "include directory" I am referring to is the <CODE>include</CODE> folder within the main SDL directory (the one that this HTML file located within). </P> <P> Now we're going to use the files that we had created earlier in the Build SDL step. </P> <P> Copy the following files into your Project directory: </P> <ul> <li> SDL.dll</li> </ul> <P> Add the following files to your project (It is not necessary to copy them to your project directory): </P> <ul> <li> SDL.lib </li> <li> SDLmain.lib</li> </ul> <P> (To add them to your project, right click on your project, and select "Add files to project") </P> <P><STRONG><FONT color="#009900">Instead of adding the files to your project it is more desireable to add them to the linker options: Project|Properties|Linker|Command Line and type the names of the libraries to link with in the "Additional Options:" box. Note: This must be done for each build configuration (eg. Release,Debug).</FONT></STRONG></P> <H3> SDL 101, First Day of Class </H3> <P> Now create the basic body of your project. The body of your program should take the following form: <CODE> <PRE> #include "SDL.h" int main( int argc, char* argv[] ) { // Body of the program goes here. return 0; } </PRE> </CODE> <P></P> <H3> That's it! </H3> <P> I hope that this document has helped you get through the most difficult part of using the SDL: installing it. Suggestions for improvements to this document should be sent to the writers of this document. </P> <P> Thanks to Paulus Esterhazy (pesterhazy@gmx.net), for the work on VC++ port. </P> <P> This document was originally called "VisualC.txt", and was written by <A HREF="mailto:slouken@libsdl.org"> Sam Lantinga</A>. </P> <P> Later, it was converted to HTML and expanded into the document that you see today by <A HREF="mailto:snowlion@sprynet.com">Lion Kimbro</A>. </P> <P>Minor Fixes and Visual C++ 7 Information (In Green) was added by <A HREF="mailto:james@conceptofzero.net">James Turk</A> </P> </BODY> </HTML>