Skip to content

Transitions don't use "inDuration" #357

@BlueCobold

Description

@BlueCobold

#224 Report

All transitions use hardcoded "inDuration" of 0.6s, although they have a constructor-parameter for it. It would further be great to have them flexible, because 0.6s is really slow for some situations and animations.

Environment

  • Xcode version (e.g. 9.1): 12.1
  • PopupDialog version (e.g. 0.5.0): 1.1.1
  • Minimum deployment target (e.g. 9.0): 13
  • Language (Objective-C / Swift): Swift
  • In case of Swift - Version (e.g. 4): 5

Dependency management

  • Dependency manager (e.g. CocoaPods): CocoaPods
  • Version (e.g. 1.3.1): 1.10.0

What did you expect to happen?

I expect to use animations to use the given constructor-parameters for animation durations or potentially be configurable

What happened instead?

They use 0.6s hardcoded in any case

UIView.animate(withDuration: 0.6, delay: 0.0, usingSpringWithDamping: 0.6, initialSpringVelocity: 0, options: [.curveEaseOut], animations: { [weak self] in

UIView.animate(withDuration: 0.6, delay: 0.0, usingSpringWithDamping: 0.6, initialSpringVelocity: 0, options: [.curveEaseOut], animations: { [weak self] in

UIView.animate(withDuration: 0.6, delay: 0.0, options: [.curveEaseOut],

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions