iOS 10 handleInputModeList issue

[pirrate]

I am trying to implement handleInputModeList that was added in iOS10. This is my code

  case Key.KeyType.keyboardChange:
   if #available(iOSApplicationExtension 10.0, *) {
     keyView.addTarget(self, action: #selector(self.handleInputModeList(from:with:)), for:UIControlEvents.allTouchEvents)
     } else {
     keyView.addTarget(self, action: #selector(KeyboardViewController.advanceTapped(_:)), for: .touchUpInside)
 }

But it doesnt work. I tried to create new button and add same target there and it worked normally. But it doesnt work with keyViews. Any idea?

[pirrate]

@archagon @AaronFW any idea how to handle it?

[AaronFW]

I haven't had much chance to try using it.

[AaronFW]

Well, I think it is because handleInputModeList(from:with) is a method of UIInputViewController but keyView is KeyboardKey Class and KeyboardKey Class is UIControl (which inherits from UIView).

Or in other words, they are different branches of UIKit, but they don't inherit the same functions.
UIKit > UIInputViewController
UIKit > UIControl

Typically when handleInputModeList is used, it is used directly in the UIInputControlView class declaration. For example, one project I looked at had
self.nextKeyboardButton.addTarget(self, action: #selector(handleInputModeList(from:with:)), for: .allTouchEvents)
In which "self" was the class KeyboardControllerView: UIInputControllerView

Though, since I am a novice at programming, the problem could be something else. :P

[pirrate]

@AaronFW I think the main reason is because @archagon rewriting events on forwardingview and handleInputModeList(from:with:) is something that it doesnt understand. Normally if i add extra UIButton to forwardingview and add same target it works without any problem. Now i dont know how to figure it out with this architecture.

[mromanuk]

@pirrate you are right, I needed to change the way ForwardingView and KeyboardKey track touch.

That allow me to do this in keyboardViewController.setupKeys():

keyView.addTarget(self, action: #selector(handleInputModeList(from:with:)), for: .allTouchEvents)
keyView.originalViewTouch = true

the originalViewTouch is a flag to use the native UIControl tracking capability instead of the Archagon keyboard tracking in ForwardingView.hitTest

[ifanchu]

@mromanuk do you mind shedding some light on how to implement this? Some code snippets maybe? Appreciated.

[ifanchu]

I think I figure it out, thanks for the tip @mromanuk

[vishal07malvi]

@ifanchu @mromanuk @archagon @AaronFW could you please let me know this issue is fixed or not? because I also having issue with
keyView.addTarget(self, action: #selector(self.handleInputModeList(from:with:)), for:UIControlEvents.allTouchEvents)
handleInputModeList, Could you please let me know what should I do with this?

[kamalupasena]

@ifanchu Can you share a code sample ?

[aalenliang]

Here is my full solution to this issue, don't know if it's the best approach. thanks for @mromanuk sharing the tips.

in KeyboardKey.swift, add originalViewTouch property:

var originalViewTouch = false

in KeyboardViewController.swift, setupKeys function:

case Key.KeyType.keyboardChange:
    keyView.addTarget(self,
                      action: #selector(handleInputModeList(from:with:)),
                      for: .allTouchEvents)
    keyView.originalViewTouch = true

and delete advanceTapped method.

in ForwardingView.swift, hitTest function:
replace

else {
    return (self.bounds.contains(point) ? self : nil)
}

with

if !self.bounds.contains(point) {
    return nil
}
if let view = self.findNearestView(point),
    let keyView = view as? KeyboardKey,
    keyView.originalViewTouch {
    return keyView
}
return self