Merge Version Changes
For example, your version log includes the following changes:
- Version 10 Added a page
- Version 11 Added a tag
- Version 12 Drew the tag on the page.
You decide that the creation of the page was a mistake, but that the creation of the tag was not. You can proceed as follows:
- Select version 9 in the table.
- Right-click to open the context menu.
- Click Switch to This Version
Changes made in versions 10, 11 and 12 vanish from the current version.
- Select version 11 in the table and right-click to open the menu.
- Click Merge Version Changes.
The tag is again part of the current version. The page does not exist and the tag is not drawn on the non-existent page.
Depending on the change you may need to re-start your application.
For this example, the same effect could have been achieved by reversing the changes in versions 10 and 12.

- An error message indicates a conflict.
The change you are making affects an unsaved change, or possibly work being done by another developer. Examine the error message for details and resolve the conflict before re-attempting this action.
- After this change, part of the application unexpectedly stops working.
The changes include a detail that may be critical to the operation, such as a changed I/O address. Restore the previous version, examine the version log in detail, then repeat your action taking care to avoid changes that will damage the application.
Merge Version Range
If you made an earlier version current, or reversed version changes, you can merge selected changes from a range of versions into your current version.
The steps are identical to those when reversing a version range. The difference is only that selected changes are merged into the current version rather than reversed from it.
To merge a version range:
- Right-click on a version marking the start of the range and select "Merge version range" from the menu.
- Right-click on the version marking the end of the range and select "Merge version range end".
- Optionally remove files from the list of changes that will be merged.
- Click Apply and provide a comment in the dialog that appears.

- An error message indicates a conflict.
The change you are making affects an unsaved change, or possibly work being done by another developer. Examine the error message for details and resolve the conflict before re-attempting this action.
- After this change, part of the application unexpectedly stops working.
The changes include a detail that may be critical to the operation, such as a changed I/O address. Restore the previous version, examine the version log in detail, then repeat your action taking care to avoid changes that will damage the application.