Changelog History
Page 3
-
v0.8.7 Changes
๐ Bug Fixes:
Issue #117 - Round buttons in alert.
-
v0.8.6 Changes
Issue #121 - Long title for alert buttons.
-
v0.8.4 Changes
๐ Bug Fixes:
Issue #131 -
EKAttributes.PositionConstraints
initializer parameter isn't referenced in implementation. -
v0.8.3 Changes
๐ Bug Fixes:
Issue #132 - Background dimmed view is NOT animating.
-
v0.8.2 Changes
๐ Bug Fixes:
Issue #119 - Entry tap gesture doesn't cancel touches inside the entry view.
-
v0.8.1 Changes
Apply a necessary fix for Xcode 10 and older than 4.2 Swift version compatibility.
-
v0.7.2 Changes
๐ Bug Fixes
numberOfLines property #111 - Allow multiple lines in image notes.
-
v0.7.1 Changes
๐ Feature - Add a way to make a specific text field first responder in
EKFormMessageView
Related issue: Best way to present keyboard #107. The window must be a key window, so setting
presentInsideKeyWindow
totrue
is necessary to achieve that goal. Likewise:SwiftEntryKit.display(entry: formMessageView, using: attributes, presentInsideKeyWindow: true)
It is recommended to set
lifecycleEvents.didAppear
to perform the keyboard showing action. For example:attributes.lifecycleEvents.didAppear = { formMessageView.becomeFirstResponder(with: 0) }
-
v0.7.0 Changes
๐ Feature - Queue of Entries
displayPriority
is no longer nested insideEKAttributes
. It has been replaced by another construct calledprecedence
.precedence
defines the manner in which a new entry is treated in case there already is another displayed entry.- ๐ See Issue #103 for feature basic requirements.
- ๐ Please review the README.md and the API documentation to gain additional information.
Backward Compatibility
๐ Be aware that
0.7.0
breaks previous releases. In order to adjust previous usage to current behavior, just replace any instance of:attributes.displayPriority = value
To the following:
attributes.precedence = .override(priority: value, dropEnqueuedEntries: false)