-
Notifications
You must be signed in to change notification settings - Fork 756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swap panes not working for 3 file comparison.... #507
Comments
Great! We welcome your pull requests. |
Created the PR - sorry if I missed anything. Also I don't seem to have the permission to link the PR to this issue. Thx. |
sdottaka
pushed a commit
that referenced
this issue
Jan 1, 2021
sdottaka
added a commit
that referenced
this issue
Jan 2, 2021
Fixed by PR #533 |
Thank you. I see I missed some changes (the translation files, and also
some code - sorry). Appreciate it if you can provide some guidelines to
follow in each commit, and I can try to get a better commit next time.
Thx.
…On Fri, Jan 1, 2021 at 8:39 PM Takashi Sawanaka ***@***.***> wrote:
Closed #507 <#507>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#507 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKKKTG5OTDDQVJV3BEVARNTSX2BOBANCNFSM4UZW4JBA>
.
|
There was nothing wrong with it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The swap panes feature only works properly with 2-file comparisons. 3 file comparisons, the middle file always remains the same when trying to swap. I cannot swap middle file.
The problem is that I cannot customize the middle file when initiating the comparison from windows explorer (selecting 3 files in windows explorer, and then using context menu to launch in WinMerge).
Would be nice to drag/drop OR to pop up (drop-down) a menu that would allow user to customize which file goes into which pane, without having to start over with new manual comparison.
Please fix this.
The text was updated successfully, but these errors were encountered: