I don't think there's a built in way to do this. It's possible that you could do this by creating a custom control, but you'd probably have to draw all of the images for the different pieces, and be able to stretch and position them manually. I'm not sure if anyone's ever done this before, but it seems like a lot of work.
Also, just to throw this out there, Apple specifically mentions this in their
Human Interface Guidelines as something
not to do:
Quote:
The standard back button gives users a reliable way to return to the previous screen, so it’s important to avoid altering the button’s behavior. In particular, you should avoid creating a multi-segment back button, such as the one shown in Figure 6-6.
Using a multi-segment back button causes several problems:
* The extended width of a multi-segment back button does not leave room for the title of the current screen.
* There is no way to indicate the selected state of an individual segment.
* The more segments there are, the smaller the hit region for each one, which makes it difficult for users to tap a specific one.
* Choosing which levels to display as users navigate deeper in the hierarchy is problematic.
If you think users might get lost without a multi-segment back button that displays a type of breadcrumb path, it probably means that users must go too deeply into the information hierarchy to find what they need. To address this, you should flatten your information hierarchy.
|
What's interesting is that they do show an image of what this might look like, but it's not clear whether this is some undocumented function of the SDK or an old prototype, or whether they just mocked up this image to give an example of what they consider a bad practice.
I'm not sure whether they'd actually reject an app over this, but they have been pretty fickle about such issues before, so it may not be worth the risk in any case.
Navigation crumb trail
Linear Mode
