Release Notes

Public

5.4.16.634: Dec 24 2014

New

GTK Plastic SCM GUI: Branch Explorer: Navigate to 'home' changeset and 'search' features have been implemented.

New

GTK Plastic SCM GUI: Branch Explorer: Implemented navigation using the keyboard: home, end, escape and arrow keys.

New

GTK Plastic SCM GUI: Branch Explorer: Added a 'properties' view on the Branch Explorer side panel. It displays information related to a single selected object on the branch explorer: name, repository, owner, creation date, replication sources, GUID and comments.

The comments text field also allows to update the comment of the selected object when modified.

New

GTK Plastic SCM GUI: Branch Explorer: Implemented date filter for the branch explorer.

New

GTK Plastic SCM GUI: Filters and conditional format rules implemented.

New

GTK Plastic SCM GUI: Preferences window implemented.

New

Mac Plastic SCM GUI: Branch Explorer: If the selected object's comments have been edited but not saved, and the focus is changed to another object, a confirmation dialog is shown to let the user save the changes or discard them before changing the selection.

New

Installer: The client file 'plastic.exe.config' will no longer be overwritten after an upgrade.

New

Installer: The installer now copies the needed firebird libraries according to the system architecture.

New

Git Sync: When a submodule was added in a branch and merged to another branch in Git, the Git Sync is reusing the same xlink in Plastic SCM, updating the target changeset only when needed (that's it, if the submodule target was also changed).

Bug

Command line client: Using exclusive checkout with xlink, the checkin operation could fail when the xlink relative path is longer than the relative path of the checkedout file.

Example:

* Xlink relative path: /src/core_engine

* Checkedout file relative path: /license.dat

Checking in the file /src/core_engine/license.dat, the operation fails with an error. Now, this case has been fixed.

Bug

GameUI: The GameUI main window was not showed properly when it was maximized on an extended desktop configuration and the secondary monitor had a resolution higher than the resolution of the primary monitor. Fixed.