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

iOS 9 Multitasking Support #10

Open
inPhilly opened this issue May 13, 2016 · 5 comments
Open

iOS 9 Multitasking Support #10

inPhilly opened this issue May 13, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@inPhilly
Copy link

It seems that this control no longer works with iOS 9 and multitasking. A keyboard can be on the screen from another app, and can stay on the screen while navigating through the app for which this control is used. A view controller may not receive the show notification for the keyboard but will still be affected by the keyboard's presence.

@dlo
Copy link
Member

dlo commented May 13, 2016

Hmm, good point. Any ideas for a fix?

@inPhilly
Copy link
Author

Somehow the bottom constraint needs to be kept as a single property throughout the app, possibly in the app delegate. So when a view controller appears and the keyboard is already showing, the constraint constant will already be set to the height of the keyboard. But I am not sure how this would work with the existing UIViewController class extension..

@inPhilly
Copy link
Author

Also, it somehow needs to be taken into account when an app is started up and it is already in splitScreen mode and the keyboard is already showing - no notification will be received at all. Now, I don't have an iPad with splitScreen/multitasking and I don't know if that is a possible real-life scenario, but it does happen when i run my app and the splitScreen with keyboard is already showing on the simulator (iPad Air 2).

@dlo dlo changed the title iOS 9 Support iOS 9 Multitasking Support May 13, 2016
@dlo
Copy link
Member

dlo commented May 13, 2016

I'll do some research. I wouldn't be surprised if there is an SDK-limitation here.

@dlo dlo added this to the 2.0.1 milestone Jul 27, 2016
@dlo dlo self-assigned this Jul 27, 2016
@dlo dlo added the bug label Jul 27, 2016
@inPhilly
Copy link
Author

No fix for this yet, huh? I would fix it if I had any ideas.

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

No branches or pull requests

2 participants