Bug: Run in new instance

[Alexo]

Version 14.0

Open a comparison of 2 files
Select "New Comparison"
Check "Run in new instance"
Click on "Empty files"
Bug: Current instance is closed

Also, after making changes to compared files, an attempt to open a new comparison will prompt to save/discard cancel.
This behaviour is incorrect since the user may want to keep the current comparison open.
The dialog should be displayed *after* the new comparison dialog, when the user clicks on "compare" or "empty files" and only if "Run in new instance" was not checked.

[psguru]

Open a comparison of 2 files
Select "New Comparison"
Check "Run in new instance"
Click on "Empty files"
Bug: Current instance is closed

This is not new in 14.0. "Run in new instance" only applies to real comparison while "Empty files" is a shortcut for closing your compared files. It may not be very intuitive but probably not a common scenario.

Also, after making changes to compared files, an attempt to open a new comparison will prompt to save/discard cancel.

Also existing behavior. Changing this would be difficult.

[Alexo]

Fair enough, but that is very misleading. Perhaps you should look into changing the labels to be more intuitive.

Please note that I did not say that those issues were unique in version 14, it is just that I encountered them that day. I am a heavy user of EDP and there are times where I encounter uncommon scenarios.

That said, please suggest how to go about the following scenarios:

First scenario:
The user is comparing two files, and wants to open a new comparison with empty files, while continuing working on the original comparison.
(In my case, those were configuration files from different versions and some elements were renamed and/or moved around, and I wanted to have another comparison in parallel with only parts of the files that I could modify without worrying about inadvertently breaking something with the original files)

Second scenario:
The user is comparing two files, and makes changes to one or both. The changes may or may not be saved (or may be partially saved). The user wants to open a new comparison but continue working on the existing one, without losing or committing the changes.

Now, I know that it is possible to just start another instance externally, but in different cases one can do so from within the program.

[psguru]

Currently, as you said, the only way to deal with these use cases is to start a new instance externally. We'll look into these scenarios more closely a bit later, and perhaps will make dealing with them easier.

[Alexo]

Thank you!

[psguru]

The latest build of 14.0 Beta contains the requested changes. Please give it a try.