So I think here is the equation: If you need precise device size, you have to rely on device model, for both built-in and external screens. To make that mapping possible, you need some method of reading the device model and search a database. Reading model number is easy for main device screen and HDMI screen (using uname(2) and I2C respectively) but AirPlay can be trickier. Building such an database is impossible for screens over Airplay or HDMI, let alone display settings on the device may also affect the results. Hence, if your only concern is the main display, read uname(2) and use a small database of Apple devices.
On Nov 26, 2013, at 22:36, Igor Elland <igor.ell...@me.com> wrote: >> Probably because there’s no way to accurately know the physical screen size >> of a device attached via AirPlay or HDMI cable. The API would break in such >> cases. >> >> (And the same argument applies to adding more / less content on iPad mini >> screen because of its physical dimensions. It’s a bad UX choice IMHO) >> >> :: marcelo.alves >> > > Precisely. > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/xcvista%40me.com > > This email sent to xcvi...@me.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
