2.1.1

This minor release makes undofx more module friendly.

An Automatic-Module-Name entry of "org.fxmisc.undo" has now been added to the undofx-2.1.1.jar manifest,
while the fat Jar undofx-fat-2.1.1.jar listed below has a module name of "undofx.fat"

2.1.0

Minor release that includes #28

2.0.0

Merged PRs:

• #27 Removes deprecated properties and their getters: nextTo[Undo/Redo]
• #26 Adds better support for UndoManager<List<C>> (Implements #25)

v1.4.0

Renamed nextToUndo/Redo to nextUndo/Redo. The earlier naming has been deprecated and will be removed in the next release.

Added a configuration option: UndoManager can preventMerge after a period of inactivity from the change stream. For example, if a user types "apple" into some area, pauses for a second, and then writes "oranges", there should not be a single change that inserts "appleorange" but two changes: one that inserts "apple" and one that inserts "orange"

Release 1.3.1

Actually adds the properties to peek at next available change for undo and redo, that were falsely advertised in 1.3.0, to the public API.

This changes the UndoManager interface to be generic in the change type: UndoManager<C>. For cases where you don't care about the new methods, you can just use a wildcard: UndoManager<?>.

Release 1.3.0

New features

• Support change annihilation.
• Properties to peek at next available change for undo and redo. Actually, I forgot to put them in the public API. Use Release 1.3.1 instead.

Incompatible changes

• undoAvailableProperty() and redoAvailableProperty() now return Val<Boolean> instead of ObservableBooleanValue.

1.2.2 Release

Update ReactFX version to 2.0-M5.

1.2.1 Release

There's a minor change in this release compared to 1.2 that make UndoManager fail faster when an expected change is not received.

1.2 Release

There is a change in how undo manager is constructed. Instead of providing an unapply function, you now need to provide an invert function that returns an inverse of a given change, such that

unapply(change) = apply(invert(change))

It is now also required that the change objects properly implement equals.

While these changes pose additional requirements on the user side, it allows the implementation to detect potential problems in the application: whenever the UndoManager is applying a change, it expects to receive the exact same change (up to equals) in the observed EventStream of changes. If this does not happen, it is very likely a problem that otherwise could go undetected.

1.1.1 Release

This is a maintenance release that only updates the ReactFX version to 2.0-M4u1.