Mercurial > sdl-ios-xcode
view VisualC.html @ 1192:54aa9aa32327
To: sdl@libsdl.org
From: Christian Walther <cwalther@gmx.ch>
Date: Fri, 18 Nov 2005 23:39:02 +0100
Subject: [SDL] Mouse position bugs on Mac OS X
The attached patch fixes a few bugs in SDL related to the mouse position
in windowed mode on Mac OS X, reproduced using the attached minimal test
program - at least here on 10.3.9, with SDL CVS from today. Could anyone
test whether the bugs exist and are fixed by the patch on 10.2 and 10.4?
1. When using OpenGL, the vertical mouse positions obtained through
events or SDL_GetMouseState() are off by one.
2. When using OpenGL, SDL_WarpMouse() inverts the y coordinate.
3. Clicks on the topmost pixel row of the window are not recognized.
1 and 2 do not occur in non-OpenGL mode, while 3 does. All three only
occur in windowed mode, not in fullscreen.
The cause for 1 and 3 is that in Cocoa, "the location of the mouse"
seems to be defined as "the location of the top left corner of the mouse
pointer's hot pixel" (this is not documented, it's just what I found out
here), which together with the fact that Cocoa's usual y coordinates
start at the bottom and increase upwards means that the y coordinate of
the mouse runs from 1 to h, not from 0 to h-1, in a window of height h.
If it does work on 10.2 and 10.4 (I'll try to test it as soon as I can,
but at the moment all I have at hand is 10.3.9), can this be applied to
the CVS?
-Christian
To: sdl@libsdl.org
From: Christian Walther <cwalther@gmx.ch>
Date: Mon, 28 Nov 2005 10:41:51 +0100
Subject: [SDL] Re: Mouse position bugs on Mac OS X
I wrote:
> I'll try to test it as soon as I can, but at the moment all I have at hand is 10.3.9
So, here are the results of my tests (with patched and unpatched
frameworks compiled with Xcode 1.5 (gcc 3.3) on 10.3.9):
On 10.1.5, my test program doesn't run because of "Undefined symbols:
SDL undefined reference to _CGMainDisplayID expected to be defined in
Carbon". I guess not supporting 10.1 was a deliberate decision then and
that's OK with me.
On 10.2.8, 10.3.9, and 10.4.0, the bugs exist as described in my
original post and are fixed by my patch. That is, there is no difference
between pre/post 10.3 and the patched version works correctly in all
combinations of GL/non-GL and windowed/fullscreen.
I therefore recommend the patch for inclusion.
-Christian
author | Ryan C. Gordon <icculus@icculus.org> |
---|---|
date | Mon, 28 Nov 2005 13:58:26 +0000 |
parents | e044e7c70a50 |
children | 4f896c20caf6 |
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>). </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 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>