Speaking of evidence for Retina Mac displays, I noticed this in the
backingScaleFactorReturns the backing scale factor.
- (CGFloat)backingScaleFactorReturn Value Returns 2.0 for high resolution scaled display modes, and 1.0 for all other cases.
Discussion There are some scenarios where an application that is resolution-aware may want to reason on its own about the display environment it is running in.
It is important to note that this number returned by this method does not represent anything concrete, such as pixel density or physical size, since it can vary based on the configured display mode. For example, the display may be in a mirrored configuration that is still high resolution scaled, resulting in pixel geometry that may not match the native resolution of the display device.
Note: For almost all common cases, developers should avoid using the backingScaleFactor as an input to layout or drawing calculations. Developers should instead use the backing coordinate space conversion methods instead, as the resulting code will more likely work consistently and correctly under both low and high resolution operation.
This API was introduced recently in Lion, but sounds very similar to the
UIScreen scale property:
scaleThe natural scale factor associated with the screen. (read-only)
@property(nonatomic, readonly) CGFloat scale DiscussionThis value reflects the scale factor needed to convert from the default logical coordinate space into the device coordinate space of this screen. The default logical coordinate space is measured using points, where one point is approximately equal to 1/160th of an inch. If a device’s screen has a reasonably similar pixel density, the scale factor is typically set to 1.0 so that one point maps to one pixel. However, a screen with a significantly different pixel density may set this property to a higher value.
I’m still very new to Mac development, but I wouldn’t be surprised if this NSWindow property gets a lot more attention as WWDC approaches.