Nope

still getting the same result.
If the modal view is called from an indexed caller like:
- (void)segmentAction

id)sender
{
NSLog(@"segmentAction: selected segment = %d", [sender selectedSegmentIndex]);
switch ([sender selectedSegmentIndex]) {
case 0:
[self flipTo

ageNum-1];
break;
case 1:
// show modal form!
[self.navigationController presentModalViewController: modalList animated:YES];
break;
case 2:
[self flipTo

ageNum+1];
break;
default:
break;
after the modal view is called and dismissed, a click on any segment always returns segmentindex 0
Display from console:
4/21/08 7:00:56 PM Transitions[3249] segmentAction: selected segment = 1
4/21/08 7:00:57 PM Transitions[3249] segmentAction: selected segment = -1
4/21/08 7:01:05 PM Transitions[3249] segmentAction: selected segment = 0
4/21/08 7:01:05 PM Transitions[3249] segmentAction: selected segment = -1
4/21/08 7:01:13 PM Transitions[3249] segmentAction: selected segment = 0
4/21/08 7:01:13 PM Transitions[3249] segmentAction: selected segment = -1
I guess a -1 is issued when my button pops back up BUT I clicked the middle button 3 times and you can see that the wrong index is reported after the modal view was displayed
if I comment out the call to display the modalview, the console reports:
4/21/08 7:04:21 PM Transitions[3273] segmentAction: selected segment = 1
4/21/08 7:04:22 PM Transitions[3273] segmentAction: selected segment = -1
4/21/08 7:04:24 PM Transitions[3273] segmentAction: selected segment = 1
4/21/08 7:04:24 PM Transitions[3273] segmentAction: selected segment = -1
4/21/08 7:04:25 PM Transitions[3273] segmentAction: selected segment = 1
4/21/08 7:04:25 PM Transitions[3273] segmentAction: selected segment = -1
If you use a button to call it (instead of something that takes an index) everything works correctly