Then why the hell in the five years of public iOS API, Apple always decided against a public API point for that?
To me, I think an API like that suggests possible fragmentation just like what plagued the system you-know-what and Apple clearly does not want that come into happening. Also, reading identifiers for released devices can be quite accurate. On Nov 26, 2013, at 21:45, Roland King <r...@rols.org> wrote: > Rubbish. > > And any reading of the Apple Dev Forums will find many messages from Apple > engineers telling you NOT to do that, NOT to guess, NOT to make assumptions > based on what you think identifiers are or are going to be and to stick to > the API points there are. They also ask people file bug reports with use > cases about why one might need the physical device screen size, which I have > done. > > On 26 Nov, 2013, at 9:41 pm, Maxthon Chan <xcvi...@me.com> wrote: > >> There is no reason for Apple to provide such an clearly redundant API point. >> Developers can somehow predict the new devices’ identifiers and the sizes >> are largely correctly guessed so a quick table look-up will work very well. >> >> On Nov 26, 2013, at 21:38, Igor Elland <igor.ell...@me.com> wrote: >> >>>> If there isn't a proper API point for it, then I'm not doing it. >>> >>> I’m quite sure there’s no public API to get the physical screen size or >>> otherwise differentiate between the regular size screen iPad and the mini. >> > _______________________________________________ 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
