On Jan 25, 2011, at 3:24 PM, WT wrote: > On Jan 25, 2011, at 8:45 PM, Dave Carrigan wrote: > >> When the docs say that a UINavigationController can be a tab in a tab bar >> interface, they mean a UITabBarController, not a UIViewController that >> happens to implement a tab bar interface. > > If that's the case, then I think they should make that distinction explicit > in the docs.
That statement doesn't make sense. There is only one tab bar controller that Apple knows about (UITabBarController). Just because you implemented a controller that supports its own version of tabs doesn't mean that the OS is going to magically realize this and cause all the correct behavior to occur. For better or for worse, from the OS point of view, yours is a generic UIViewController with all of the capabilities and restrictions that that implies. And one thing that hasn't been explicitly mentioned is that Apple has a tendency to make changes to class implementations for any number of reasons. Their only responsibility to you as a developer is to maintain their API interface contract and documented behavior. If you go coloring outside the lines, you could find yourself having to do ongoing maintenance of your source to fix issues that shouldn't have been issues in the first place. steve _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
