Original inset can be loosed #8

Merged
merged 1 commit into from Feb 2, 2012

Conversation

Projects
None yet
3 participants

jfradj commented Feb 2, 2012

When the user pass from on textfield to another one directly, no keyboard events are called.
But if those two textfields haven't the same type of input view (for instance, one with the default keyboard and one with a custom view) so only a KeyBoardWillShow event is thrown (it isn't balanced with a KeyBoardWillHide) and then the _priorInset will saved the current inset which is the modified one (not the original one).
Tell me if you want a sample code.

@jfradj jfradj Prevent the loose of the real initial Inset.
When the user pass from on textfield to another one directly, no keyboard events are called.
But if those two textfields haven't the same input views so only a KeyBoardWillShow event is thrown (it isn't balanced with a KeyBoardWillHide) and then the _priorInset will saved the current inset which is the modified one (not the original one).
b1c4348

michaeltyson merged commit 709b08c into michaeltyson:master Feb 2, 2012

jfradj commented Aug 14, 2013

Hi there,

In the last version, the issue had reappeared.

My previous patch is still valid.

Thanks

Thank you jfradj, this just fixed the issue I was seeing.

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