Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tokenFieldDidBeginEditing: not called as expected #48

Open
bryanoltman opened this issue Jan 23, 2015 · 4 comments
Open

tokenFieldDidBeginEditing: not called as expected #48

bryanoltman opened this issue Jan 23, 2015 · 4 comments

Comments

@bryanoltman
Copy link

To reproduce, implement tokenFieldDidBeginEditing: and remove the call to [self.tokenField becomeFirstResponder]; in the sample project's ViewController.m. Launch the app, tap the token field, and notice that tokenFieldDidBeginEditing: is never called.

@ayanonagon
Copy link
Contributor

Sorry for the delay, looking at this now. :octocat:

@bryanoltman
Copy link
Author

No worries! I added a not-quite-perfect fix (the begin/end editing methods get called multiple times) in this fork. Not sure if that will help, but the editing property in VENTokenField would be where to look.

@ayanonagon
Copy link
Contributor

Thanks for the link to the fork! Yeah I’ve been struggling to find an elegant way to fix this. I’ve gone down some rabbit holes of UITextFieldDelegate method hell. I think it might be the case that we need some sort of state to keep track of whether or not that delegate method should be called (I’m guessing that’s what the editing property is essentially tracking?).

@andrewjburnett
Copy link

@ayanonagon Any fix? How can you go about making the tokenField firstResponder in response to a touch event?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants