-
Notifications
You must be signed in to change notification settings - Fork 10
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
WinMerge 2011.211.110 broke filter functionality #14
Comments
…14) / Bycatch from incomplete earlier commit
Thanks for your bug report. You may want to try the CI build at https://ci.appveyor.com/project/datadiode/winmerge2011/builds/38108231/artifacts. |
I've looked at at version 0.2011.211.119, and the problem seems to be fixed only partially… A filter existing in the defined folder is not recognized automatically. I have to choose the I'm not sure why the behavior of the filter menu had to be changed at all? It was working in previous versions, was there any reason to touch this part of the application? Thanks for restoring the original functionality! ☺ |
With the new version released some days ago, the file filter functionality during comparison of folders is broken (I use the portable installation):
New…
(just tested private filters, not shared ones). I can still add one, the file with the filter definition gets created successfully, but after saving it's not listed in the UI and cannot be selected.Install…
. After providing the path to an existing filter definition, I just receive an error message ("Installing filter file failed. Could not copy new filter file to filter folder.").And finally the default path has changed? I previously stored my definitions in
C:\Users\‹Username›\Documents\WinMerge\Filters
, but now WinMerge stores the filters apparently in theProgramData\WinMerge\Filters
sub directory of its (portable) installation path? Copying an existing filter definition to this path also doesn't help.Can anyone confirm my findings? In case this is really a nasty bug, can it please be fixed? Thanks!
The text was updated successfully, but these errors were encountered: