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.

Use the Xcode command files (located in the Xcode-iOS/build-scripts folder)

to conveniently generate a workspace for Xcode 3 or Xcode 4. It also

contains a cleaner script and a convenient script for automatically

running all the test suites.

The iOS project will be referencing all files related to the top-level iOS

project. The core library will use the top-level include and src directories,

just like the other generated projects, but it will build projects for each of

the Demos in the top-level Xcode-iOS folder. These projects will have any

resources they need copied to be copied over and included as resources. They

will also reference the Info.plist file in Xcode-iOS/Demos.

iOS support is currently experimental, but it should work just fine for any and

all applications. All of the demos that work from the manually-created Xcode

projects also work for the generated projects. There are a few minor things that

need improving, but nothing major.

The iOS projects have no major dependencies other than the ones in the manual

Xcode-iOS project. Those are:

  -AudioToolbox.framework

  -QuartzCore.framework

  -OpenGLES.framework

  -CoreGraphics.framework

  -UIKit.framework

  -Foundation.framework

  -CoreAudio.framework

  -CoreMotion.framework

All of these frameworks are part of the iOS SDK, not part of the core OS X

system.

Run the clean script to clear out the directory of Xcode-related files

and binaries.