Community
Participate
Working Groups
The condition when a filter is activated and when a filter is deactivated needs to be the other way around. Currently a filter is deactivated when the boolean variable "toMakeActive" is true. This is clearly wrong.
Patches are welcome
Probably is to be fixed in NavigatorFilterService#setActive(..), to match the usage we see in ToggleFilterAction#run()
I have a patch pending and will submit it soon
Thanks Jan. This indeed seems to be a bug. Do you have any example of workflow that highlight this bug in the user perspective?
It seems as if the class ToggleFilterAction which is the only class which calls the method setActive(String aFilterId, boolean toMakeActive) on the NavigationFilterService is not used anywhere. Therefore I think that currently no workflow exists to highlight this bug. Only when I implement the MRU filters feature I make use of the ToggleFilterAction and the bug surfaces.
New Gerrit change created: https://git.eclipse.org/r/81880
Gerrit change https://git.eclipse.org/r/81880 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=96280fa5b5aa768a44b6815591c97121f6d46ad6
Patch merged, thanks Jan!