Bug using ContactPicker about titokenfield HOT 5 CLOSED

Weirdly, in using my own picker, I haven't seen this behaviour - but I don't call resignFirstResponder on the field manually.

I've changed the addToken method to make the field become first responder before adding the token. Seems to work.

from titokenfield.

Sorry, for the confusion. Your last fix didn't really help with this problem.

The solution was to change the call order in the picker delegates. First the picker view needs to be dismissed and then the addToken method should be used. This way everything works fine. If you try to add a token before dismissing the picker it will screw up the results.

from titokenfield.

I'm confused a little; You're saying it's nothing to do with the TITokenField? You just needed to change some stuff in your own code?

from titokenfield.

It has something to do with TITokenfield and the issue is related to the responder chain.

I'm using the built in people picker and this way it won't work:

- (BOOL)peoplePickerNavigationController:(ABPeoplePickerNavigationController *)peoplePicker
      shouldContinueAfterSelectingPerson:(ABRecordRef)person {

    [tokenFieldView.tokenField addToken:@"SomeName"];
    [self dismissModalViewControllerAnimated:YES];  
    return NO;
}

The reason for this is that the addToken method won't work correctly as long as another UI element is first responder, because all tokenNames need to be drawn before another one can be added. Changing the order in this example and first dismissing the modal view and then using addToken works just fine.

from titokenfield.

Oh I see - well for now, obviously just swap the lines so it works.

I'll keep looking into it.

from titokenfield.