I'm trying to setup a UIView animation to match the keyboard animation, including the animation curve. .animationCurve is available from Typist.KeyboardOptions, but I'm getting a type error. Any way around this?

UIView.animate(withDuration: options.animationDuration, delay: 0, options: options.animationCurve, animations: {
    self.view.layoutIfNeeded()
}, completion: nil)

Cannot convert value of type 'UIViewAnimationCurve' to expected argument type 'UIViewAnimationOptions'

Added input accessory view support (#15) by adding a scrollView property to track panning. You also need to set the inputAccessoryView on the textField.

Observes the input accessory view through the willChangeFrame and didChangeFrame observer.

Demo has been updated to reflect the changes.

// keyboard input accessory view support
textField.inputAccessoryView = UIView(frame: toolbar.bounds)
keyboard.scrollView = tableView

// keyboard frame observer
keyboard.on(event: .willChangeFrame) { [unowned self] options in
    let height = UIScreen.main.bounds.height - options.endFrame.origin.y
    self.bottom.constant = max(0, height - self.toolbar.bounds.height)
    UIView.animate(withDuration: 0) {
        self.tableView.contentInset.bottom = max(self.toolbar.bounds.height, height)
        self.tableView.scrollIndicatorInsets.bottom = max(self.toolbar.bounds.height, height)
        self.view.layoutIfNeeded()
    }
}.start()

Im also considering an alternative implementation like BABFrameObservingInputAccessoryView.

Same issue as #35, the problem is that SPM reads Github releases and cannot find 1.4.3.

Just add 1.4.3 release to fix it.

It works here: https://github.com/tymofiidolenko/Typist/releases/tag/1.4.3

I have XCode 12.5

I'm aware of the current limitations of using a singleton instance and start/stop methods to setup and remove listeners.

I'm opening this issue to start conversation about how to best address this limitation so that multiple typist instances can be setup at the same time for example from a full screen view controller on the iPad and another modally present page view controller that is occupying just part of the screen (page modal view controller)

Quickly thinking out loud I think it should be possible instead of using a singleton just instantiate and start typist in viewDidLoad and stop it in deinit...

Any thoughts on this?

Thanks Martin

Since callbacks only stores one closure of each event type, multiple controllers that use Typist.shared will "fight" over who receives notifications.

class ControllerOne: UIViewController {
  override func viewDidLoad() {
    Typist.shared.on(event: .willShow) { _ in print("will show from one") }
  }
}

class ControllerTwo: UIViewController {
  override func viewDidLoad() {
    Typist.shared.on(event: .willShow) { _ in print("will show from two") }
  }
}

If both of these controllers are loaded, only the second controller will get the notifications.

Easy fix: remove the singleton, and have each controller retain its own Typist instance.

When there's no need to store the result of the last .on(:_,:_) function call, the warning is raised. Fixed that. Looks like in most cases this behaviour is more practical.

Could you please add support for SPM in Xcode 11? Currently Xcode gives the error 'has no Package.swift manifest for version 1.4.2' when adding the package to the Xcode project.

Seems like lot of constants have changed, 'UIApplicationDidBecomeActive' has been renamed to 'UIApplication.didBecomeActiveNotification' 'kCAFillModeBoth' has been renamed to 'CAMediaTimingFillMode.both' 'UIApplicationDidBecomeActive' has been renamed to 'UIApplication.didBecomeActiveNotification'

and a few more

This adds support for SwiftPM manifest based dependency managers. Specifically this adds support for installing via Accio but will probably also work with SwiftPM once it's integrated into Xcode.

In order to smoothly animate our views at par with iOS keyboard, we must useUIView.animate(withDuration:delay:options:animations:completion:) method which takes UIViewAnimationOptions as it's options argument value.

Right now we must convert KeyboardOptions.animationCurve from UIView.AnimationCurve to UIView.AnimationOptions in order to call our animate function.

To make our lives easier and our code cleaner, I've implemented a helper variable called animationOptions in Typist.KeyboardOptions struct, which transforms a given UIView.AnimationCurve to its respective UIView.AnimationOptions value.