ayrkm

8 ms·

1. 1.▲
   by ayrkm 5y ago

   That is called taking risk and pushing the limit. If it does not work, admit and learn then move on.
2. 2.▲
   by ayrkm 11y ago

   i keep my options open until I find a better solution. i'm assuming engineers that build FB messenger, WhatsApp, Twitter etc. could be using similar approach, but I am more than happy to be proven wrong.
3. 3.▲
   by ayrkm 11y ago

   will do and hope Apple may do something about that. until then, will stick to current solution and test ahead of any new iOS release.
4. 4.▲
   by ayrkm 11y ago

   yes, that I agree, it may break between iOS versions. i'm all ear to other approach if any
5. 5.▲
   by ayrkm 11y ago

   Hi sandofsky, that was our previous implementation (dismissal starts only when user's touch enters the real keyboard area) - it doesn't feel 'right'. The library is not really using KVO to observe private APIs, bounds&#x
6. 6.▲
   by ayrkm 11y ago

   Hi, it works in iOS 9. The Pie for iPad screenshot in the post is running in iOS 9.
7. 7.▲
   by ayrkm 11y ago

   I could've more explicit. Interactive dismissal only made possible with UIScrollViewKeyboardDismissModeInteractive introduced since iOS 7. This article described solution for interactive dismissal with `sticky` input field atop the key
8. 8.▲
   by ayrkm 11y ago

   hi Aaron, I did briefly look at SlackTextViewController. But decided not to use it because the project contains many features that we do not need. Furthermore, it doesn't support usage on iPad.
9. 9.▲
   by ayrkm 11y ago

   Thanks, glad you find it useful.
10. 10.▲
    by ayrkm 11y ago

    It's because the input field will always appear at window level above the level of key window. So, if you need to show overlay in key window, the input field will appear above the overlay. Example for such overlay could be a loading in
11. 11.▲
    Implementing a Sticky Input Field in iOS(medium.com)

    58 points by ayrkm 11y ago|18 comments