>> The only workaround I was able to get working was to call a private >> AppKit method to fix up the layer geometry. > > Which is a no-no, and shouldn’t be done. Bad Kyle. No biscuit.
Forgive me for raising such a taboo topic, but I've encountered situations where I had to choose between A) using a private API, B) shipping a product with a malfunction that would aggravate users to a greater degree than the risk of using the private API, or C) not shipping a product. Certainly – placing yourself in the shoes of a third-party developer – you would agree that situations exist where using a private API is warranted? I'd be happy to provide specific examples as necessary. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
