INSTALL.txt
author Sam Lantinga <slouken@libsdl.org>
Sun, 17 Aug 2014 14:57:52 -0700
changeset 9086 c5e33f9a0d03
parent 9025 d09d4b578e77
child 10893 54480745c410
permissions -rw-r--r--
Fixed bug 2655 - OSX: Window position and global mouse coord spaces are different

Tim McDaniel

On OSX, with revision 8729, the coordinate space for window position and the coordinate space for global mouse position don't match. For a non-fullscreen window, the window position is global relative to the bottom of the menubar. The global mouse position is relative to the top of the screen. This affects Cocoa_WarpMouse and potentially other things as well. Further, the coordinate system for window position is now affected by what screen it is on. For example, if I have two equal size screens oriented side by side such that the tops of the screens are equal in global space, with the menubar on one screen, and a window straddles the two screens, the window's y position makes no sense. The window's y position depends on what screen "most" of the window is on. So if I move the window horizontally just a bit, the y position of my window is now different by the size of the menubar, even though the window was not moved vertically.

I'd like to reiterate that this was a fairly fundamental change (and a breaking change for us). If SDL OSX is to really support multi-display configurations, this is especially problematic.

If the real concern is preventing windows from going under the menubar, then perhaps a solution involving something like overriding [NSWindow constrainFrameRect] would be less problematic than redefining the global window coord space for the main display.
slouken@7222
     1
slouken@7222
     2
To compile and install SDL:
slouken@7222
     3
slouken@7227
     4
    1.  Windows with Visual Studio:
slouken@7227
     5
        * Read VisualC.html
slouken@7222
     6
slouken@7227
     7
        Windows with gcc, either native or cross-compiling:
slouken@7227
     8
        * Read the FAQ at http://wiki.libsdl.org/moin.fcg/FAQWindows
slouken@7227
     9
        * Run './configure; make; make install'
slouken@7222
    10
slouken@7227
    11
        Mac OS X with Xcode:
slouken@9025
    12
        * Read docs/README-macosx.md
slouken@7222
    13
slouken@7227
    14
        Mac OS X from the command line:
slouken@7227
    15
        * Run './configure; make; make install'
slouken@7227
    16
slouken@7227
    17
        Linux and other UNIX systems:
slouken@7227
    18
        * Run './configure; make; make install'
slouken@7227
    19
slouken@7227
    20
        Android:
slouken@9025
    21
        * Read docs/README-android.md
slouken@7227
    22
slouken@7227
    23
        iOS:
slouken@9025
    24
        * Read docs/README-ios.md
slouken@7227
    25
slouken@7227
    26
        Using Cmake:
slouken@9025
    27
        * Read docs/README-cmake.md
slouken@7222
    28
slouken@7222
    29
    2.  Look at the example programs in ./test, and check out the online
slouken@7222
    30
        documentation at http://wiki.libsdl.org/
slouken@7222
    31
slouken@7222
    32
    3.  Join the SDL developer mailing list by sending E-mail to
slouken@7222
    33
    	sdl-request@libsdl.org
slouken@7222
    34
        and put "subscribe" in the subject of the message.
slouken@7222
    35
slouken@7222
    36
        Or alternatively you can use the web interface:
slouken@7222
    37
            http://www.libsdl.org/mailing-list.php
slouken@7222
    38
slouken@7222
    39
That's it!
slouken@7222
    40
Sam Lantinga <slouken@libsdl.org>