As I've stated elsewhere, it's almost never a good idea to get rid of the core navigational classes that are provided by UIKit
. What type of application requirements do you have that you think merit a completely custom tab bar class? It's almost always possible to achieve the necessary customizations by either subclassing, categorizing, or making use of layers.
UPDATE 1: So here's what I did in some of my apps to get a custom tab bar implementation.
- Create a subclass of
UITabBar
- Add a method to your custom subclass called something like
-updateTabBarImageForViewControllerIndex:
- In Interface Builder, change the class of your tab bar controller's tab bar to your custom subclass
- In whatever class conforms to your tab bar controller's delegate (e.g., your app delegate), implement
-tabBarController:shouldSelectViewController:
and call -updateTabBarImageForViewControllerIndex:
on your custom tab bar subclass
Basically, you want to notify your tab bar subclass every time the tab bar controller is about to switch view controllers. When this happens, determine what image you need to choose for your tab bar. You should have n
images for your tab bar, one for the selected state of each tab. It's possible to actually fudge the implementation of UITabBarItem
and just work with individual images, but it's a little more work.
// MyAppDelegate.m
- (BOOL)tabBarController:(UITabBarController *)tabBarController shouldSelectViewController:(UIViewController *)viewController
{
// Determine the index based on the selected view controller
NSUInteger viewControllerIndex = ...;
[(MyTabBar *)tabBarController.tabBar updateTabBarImageForViewControllerIndex:viewControllerIndex];
return YES;
}
// MyTabBar.m
- (void)updateTabBarImageForViewControllerIndex:(NSUInteger)index
{
// Determine the image name based on the selected view controller index
self.selectedTabBarImage = [UIImage imageNamed:...];
[self setNeedsDisplay];
}
- (void)drawRect:(CGRect)rect
{
CGContextDrawImage(UIGraphicsGetCurrentContext(), rect, self.selectedTabBarImage.CGImage);
}
UPDATE 2: Now that I think about it more, you actually could (and should) get away with what you're trying to achieve without subclassing UITabBar
at all. Import <QuartzCore/QuartzCore.h>
and take advantage of layer contents. :)
// MyAppDelegate.m
- (BOOL)tabBarController:(UITabBarController *)tabBarController shouldSelectViewController:(UIViewController *)viewController
{
// Determine the image name based on the selected view controller
CGImageRef newTabBarImageRef = [[UIImage imageNamed:...] CGImage];
tabBarController.tabBar.layer.contents = (id)newTabBarImageRef;
return YES;
}
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…