-
Notifications
You must be signed in to change notification settings - Fork 798
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
New filter (F) display #1281
Comments
Along the lines of Pierre's feedback... any thoughts of how to make it more clear to the user what the A matching Explanatory text in a tooltip for the tab could also be good, but it would not appear when the tab bar is disabled, which is how I generally keep WinMerge configured. So far, the idea I've come up with that I like the most is to add a toolbar button that toggles filters on/off. The icon could be the letter Thoughts? |
For a), in version 2.16.20, "(F)" is now displayed on the left side. |
@sdottaka What do you think of the idea of adding a toolbar button to toggle filters (and indicate the filter state)? I find that toggling filters on/off is a common action to perform. This is especially true because file extensions generally don't provide enough information to WinMerge (or any application) regarding the specific type of text file being compared. |
I think the idea is good, but the toolbar we have now has so many icons that I don't want to add to it. |
Thanks. I just realized that is also a "P" for active prediffer .. |
On my 24" screen it covers only 1/3 of it's width. |
I like the new "(F)" that displays that a filter is active. Two small remarks:
a) It is also displayed in the tab - see here:
When there are looooong filenames, not only the filenames are truncated, also the (F) disappears. maybe there is a better way to display it always?
b) It seems that it is only displayed when the filter is "active"; it is not displayed when the filter is "switched on, but is inactive". I'm not sure if it would be better to display these different situations for better usage....
The text was updated successfully, but these errors were encountered: