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

Keyboard issues #9

Open
soffes opened this issue May 31, 2011 · 4 comments
Open

Keyboard issues #9

soffes opened this issue May 31, 2011 · 4 comments

Comments

@soffes
Copy link

soffes commented May 31, 2011

I've noticed when DCIntrospect is enabled, the keyboard will not animate in correctly. Also sometimes settings becomeFirstResponder doesn't work or does work and the keyboard is not visible.

Not a huge deal, just noticing.

@domesticcatsoftware
Copy link
Owner

I think this is because the keyboard is already "up" all the time even though it is invisible (inputTextView.inputView is an empty view). So the system doesn't animate it up, similar to how when you switch from a text field directly to another in other apps the keyboard stays up in between.

Not sure why becomeFirstResponder isn't working though, I'll try to reproduce it to fix that.

@schwa
Copy link

schwa commented Feb 3, 2012

Seeing this too - even if we're not enabling DCIntrospect.

It would be really nice if there was a way to include DCIntrospect in code but have it not run at all. We wrapped the code with

#if USE_DCINTROSPECT == 1
    [[DCIntrospect sharedIntrospector] start];
#endif

And DCIntrospect was still firing with the constant at 0.

@schwa
Copy link

schwa commented Feb 3, 2012

Actually I'll file this as a new bug.

@daanvanhasselt
Copy link

I've also noticed some 'glitches' with keyboard animations, though becomeFirstResponder is working fine. Keyboard does not animate in but just appears, and when hiding the keyboard it starts to animate out but then flashes briefly in the upper right corner of the screen.

timd pushed a commit to timd/DCIntrospect that referenced this issue Dec 3, 2012
Handle responses with no content (ex. http status code 204)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants