• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FYI - Resolution Independence
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI - Resolution Independence


  • Subject: Re: FYI - Resolution Independence
  • From: Ricky Sharp <email@hidden>
  • Date: Sat, 27 Oct 2007 07:15:44 -0500


On Oct 27, 2007, at 7:05 AM, Alastair Houghton wrote:

On 27 Oct 2007, at 12:47, Ricky Sharp wrote:

I'm not angry that I spent time making my app res-ind (been doing so since the Tiger tech talk back in 2004). But, I'm quite disappointed this feature has not made it to prime time. I'll continue ensuring my app works well will other scaling factors in hopes the feature may one day return. And, will still file bugs.

I thought Apple had always made clear that resolution independence, as an end-user feature, would "go prime time" when high-dpi panels were shipping in their machines.

Well, they already ship such panels. I don't have the slide handy, but I remember looking at the entire product lineup, and I believe the highest dpi device is now hovering around 200 dpi.


I don't think it was ever the intent (at least, as far as I'm aware) to provide an end-user UI for it before that point, and my guess is that even when high-dpi panels are shipping with Apple machines, resolution independence will be *primarily* an automatic feature (i.e. you plug-in a high-dpi panel, and that panel runs with a non-1.0 scale factor). It seems to me that the idea of getting us to get our apps to support RI *now* is that, when the high-dpi panels become readily available, everything will "just work" in the usual way that people expect with Apple kit.

I suppose I'm surprised that you're surprised.

I'm not surprised, just a bit disappointed. Other than the NSCursor issue, framework scaling is working as advertised.


(The only query I have really about RI is what happens with machines that have a normal panel and a high-dpi panel... presumably someone at Apple has thought this through, or is doing so right now.)


You mean dual monitors? It should "just work". After all, if your app draws to points and not pixels, it is now "resolution independent". One square inch worth of graphics your app draws will occupy a physical inch on either monitor, no matter what the individual monitor's dpi is.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

_______________________________________________

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


  • Follow-Ups:
    • Re: FYI - Resolution Independence
      • From: "John C. Randolph" <email@hidden>
    • Re: FYI - Resolution Independence
      • From: Alastair Houghton <email@hidden>
References: 
 >FYI - Resolution Independence (From: Ricky Sharp <email@hidden>)
 >Re: FYI - Resolution Independence (From: Alastair Houghton <email@hidden>)

  • Prev by Date: Re: FYI: Aqua Icon Kit for 512x512 cursors
  • Next by Date: Re: Issue with custom view in Interface Builder 3?
  • Previous by thread: Re: FYI - Resolution Independence
  • Next by thread: Re: FYI - Resolution Independence
  • Index(es):
    • Date
    • Thread