And as expected this has been pushed back at me: "Works as expected". Apple doesn't mind at all if the very same app with the very same code compiled against the very same SDK draws its text in completely different places under different systems. m.
> Date: Mon, 29 Oct 2012 08:43:14 -0700 > From: Matt Neuburg <[email protected]> > > I've filed a bug on this, clearly demonstrating the problem (the very same > code compiled against the very same SDK draws the text in a very different > location); but it is obvious that nothing will be done about it. There are > pervasive changes in text drawing throughout iOS 6, and backward > compatibility has never been a priority. m. > > On Fri, 12 Oct 2012 09:46:21 -0700, Matt Neuburg <[email protected]> said: > >> What about the above part of my original question? This is a serious issue, >> because it basically means that the text appears in a different place under >> iOS 5 vs. iOS 6. You can easily see this by making a simple CATextLayer in a >> project whose base SDK is iOS 6 but whose deployment target is iOS 5. Run in >> the Simulator using an iOS 6 destination and then using an iOS 5 destination >> and you will see that the text has moved significantly. So using CATextLayer >> in a backward-compatible project is going to be a massive headache. m. -- matt neuburg, phd = [email protected], http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
