Re: Custom keyboard with search bar not behaving
On Aug 20, 2018, at 13:35, Saagar Jha wrote: > > What does [UIApplication.sharedApplication.keyWindow > performSelector:@selector(firstResponder)] give you? It correctly shows it to be the UITextView I currently have in the wrapper app, both before and after I activate and cancel the search bar. It seems like the UIInputViewController's textDocumentProxy isn't handling the change in input views properly. Steve via iPhone ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Custom keyboard with search bar not behaving
What does [UIApplication.sharedApplication.keyWindow performSelector:@selector(firstResponder)] give you? Saagar Jha > On Aug 20, 2018, at 06:16, Steve Mills wrote: > > I guess I'll try this list as well. > > I’m implementing a custom keyboard for iOS. It contains a UISearchBar the > user can use to filter the “keys” they can use to type. When the search > button is used, I call [searchBar resignFirstResponder] to have the search > bar give up its capture of input. The insertion point has been and still will > be blinking in the document view, yet calling [self.textDocumentProxy > insertText:s] no longer inserts text into the document. > > I thought this was working earlier in the project development. Any ideas? I > see a similar feature working in Google's Gboard. Maybe I need to use a fake > search bar so the text input chain never gets disturbed? > > BTW, I've only tested from the Simulator available on my work Mac, which is > still maddeningly stuck on macOS 10.10. > > -- > Steve Mills > Drummer, Mac geek > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/saagar%40saagarjha.com > > This email sent to saa...@saagarjha.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Custom keyboard with search bar not behaving
I guess I'll try this list as well. I’m implementing a custom keyboard for iOS. It contains a UISearchBar the user can use to filter the “keys” they can use to type. When the search button is used, I call [searchBar resignFirstResponder] to have the search bar give up its capture of input. The insertion point has been and still will be blinking in the document view, yet calling [self.textDocumentProxy insertText:s] no longer inserts text into the document. I thought this was working earlier in the project development. Any ideas? I see a similar feature working in Google's Gboard. Maybe I need to use a fake search bar so the text input chain never gets disturbed? BTW, I've only tested from the Simulator available on my work Mac, which is still maddeningly stuck on macOS 10.10. -- Steve Mills Drummer, Mac geek ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
