+2

Conflict Solver (or Index Editor): reuse existing window instead of opening new one

Thomas Singer 1 year ago updated by Alexander Miloslavskiy 1 year ago 1

Having a Conflict Solver open for a.txt, invoking the Conflict Solver a second time for a.txt should switch to the existing Conflict Solver window instead of opening a new one.

+1

When solving a difficult conflict (sometimes it takes more then 10 minutes to understand how to solve), it's easy to forget that Conflict Solver window is already open and open a new one. That easily becomes confusing, especially if some conflicts were already solved in previous window.


Having SmartGit re-activate the old window instead of opening a new window will solve that.