0.3.3

What's Changed

• Non-animated updates shouldn't wait until the next turn of the run loop #26 by @jtrivedi in #27

Full Changelog: 0.3.2...0.3.3

0.3.2

Fixes a display link crash reported here: #30

0.3.1

This revision fixes an issue with animating and re-targeting affine scale and translation.

0.3.0

Version 0.3.0 adds macOS as a supported platform for Wave, and enables first-class animation support for AppKit.

AppKit apps can now use both the block-based and property-based animation APIs. There's also a tiny sample app for reference. In a separate patch, I'll add NSView support, so you can animate frame, bounds, etc., and not just properties on CALayer.

Other improvements/additions:

• Support for animating CALayer.borderColor/borderWidth
• Significantly improved color animation (UIColor and NSColor)
• Fixed a retain cycle/leak

API compatibility notes:

• UIView.animator.backgroundColor and CALayer.animator.backgroundColor are both non-null. If you want to animate to a clear/transparent color, animate to UIColor.clear instead of to nil.

0.2.1

Support 120 fps animation on ProMotion devices.

0.2.0

Version 0.2.0 renames the Animation class to SpringAnimator, which enables Wave to be used with SwiftUI.

Due to the API renaming, this version is a breaking change. However, there are only two types that have been renamed, so clients shouldn't have too much difficulty updating to the new name.

Please reach out if you experience any difficulty adopting the new version.

0.1.1

Add three new animatable properties: shadowColor, shadowRadius, and shadowOffset.

0.1.0

Commit docs site