We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 700 - SDL does not find Quartz and mouse grabbing
Summary: SDL does not find Quartz and mouse grabbing
Status: RESOLVED DUPLICATE of bug 581
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: don't know
Hardware: PowerPC Mac OS X 10.5 (Intel)
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 15:47 UTC by misterblairo
Modified: 2009-08-30 08:34 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description misterblairo 2009-02-13 15:47:05 UTC 
When launching a simple basic SDL application that use SDL-1.2.13 and compiled without any errors on Mac OS X 10.5, the system warns about using NSQuickDrawView instead of QuickDraw, so that I should move to Quartz. On Mac OS X, SDL normally work with Quartz. But no doubt Quartz is install and in work on my system.  Basically, this bug/problem has no very major consequences on the application working. Only the mouse position seems not to be normally interpreting. In fact, the SDL_WarpMouse function just not work. The displaying work normally as far as I saw.
This report is simply write, but it may have, and I really believe that, others no-visible, or no-use in this basic application, consequences.
Comment 1 mjbmon 2009-04-12 10:11:42 UTC 
I was able to verify this bug on Mac OS X 10.5.6 with SDL 1.2.13. The message is

Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.

However, SDL_WarpMouse appears to work fine.
Comment 2 John Barberio 2009-08-30 08:34:01 UTC 

*** This bug has been marked as a duplicate of bug 581 ***