Re: NSScreen + resolution change
Re: NSScreen + resolution change
- Subject: Re: NSScreen + resolution change
- From: John Stiles <email@hidden>
- Date: Wed, 18 Jul 2007 10:08:17 -0700
It has been a long time since I had to deal with this, but I think
the results from NSScreen will correct themselves if you let the
event loop run after the mode change takes effect.
On Jul 18, 2007, at 9:10 AM, Uli Kusterer wrote:
On 18.07.2007, at 13:50, Thomas Engelmeier wrote:
that's what I already came up with, but fear as soon NSScreen is
fixed to behave as documented it will break..
*sigh*
You could try to drop down to CGDirectDisplay or so. There's some
CGxxx calls to list all screens and get their rects, with some luck
those don't do the errant cacheing you see in NSScreen (If not,
there's always Quickdraw's GDHandle...). You might be able to
detect whether the bug is still there by checking what CG gives you
against what NSScreen gives you, and then only apply your manual
fix when they differ.
If Quickdraw is your only route to detect this, that's OK too:
Quickdraw is still available, and unless you need to go 64-bit,
will probably be available until the fix gets shipped with a MacOS
version. So, by the time you need to get rid of that Quickdraw
code, you may not need the fix anymore anyway.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
40blizzard.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden