Re: FYI - Resolution Independence
Re: FYI - Resolution Independence
- Subject: Re: FYI - Resolution Independence
- From: Alastair Houghton <email@hidden>
- Date: Sat, 27 Oct 2007 14:48:27 +0100
On 27 Oct 2007, at 14:34, Emanuele ∞ Vulcano wrote:
Il giorno 27/ott/07, alle ore 15:22, Ricky Sharp ha scritto:
I believe the frame buffer always contained a representation to
draw on the highest bit-depth display and then downsampled when
rendered on other displays. Same should hold true for RI;
downsample the portions to render on lower-dpi displays.
It could also ask a view to drawRect: different portions of it with
different scaling coefficients, which would probably look better.
There are a lot of ways to work around the problem.
Yeah, I'm not sure it's quite that simple, actually. For instance,
what happens if you use NSCopyBits() or similar? And how do you deal
with the problem of pixel-alignment rounding in such a case? For
instance, it might result in a horizontal line having an obvious kink
where it goes across the displays. There are other problems too (for
instance, if a view stores any pixel co-ordinates, it could end up
with some with one scale factor applied and some with a different one).
It's actually quite a hard problem to solve in a good way. Ricky's
solution is a possibility, though I think we all know that downscaling
automatically wouldn't produce the best results; looking at the
NSWindow API, I believe Apple has already used a similar solution for
the case where a window overlaps screens that have different display
depths.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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