A proposal to make the "Filter Bar" shortcut toggle the visibility of the bar (rather than just show it, as it is currently) is here: https://git.reviewboard.kde.org/r/118719/

About the removal of the "Close" button: I still don't know what's best, or if the "Close" button is really as evil as you say. I think the usability experts should decide - if they think that the button should be removed, then we can do it, and I will forward any future complaints about the removal of the button to those who have proposed it

Fri13 wrote:

Removing the close button won't help if someone did not remember where in the menu they clicked to show the filter bar, or if they hit the shortcut accidentally (I don't know if this is a common phenomenon, but sometimes I hit some shortcut accidentally which triggers a feature that I never heard of, and then I have to spend some time to figure out how to revert that change).

They do remember it unless they mistakenly went to the menu and clicked the option. And that example you gave works for everything as if user does unknowingly something by mistake, then reversing it is challenge to anyone no matter of the skills as they first need to knowledge what just happened, why it happened and then find way around.

The shortcut accident is very flawed actually. Normal people have even hard time to press two keys simultaneously like Ctrl+X and Ctrl+V.

Maybe I'm not normal then. I'm not saying that these shortcut accidents happen very often to me, but when they happen, and there is no obvious way to revert the change, then this annoys me

Fri13 wrote:Should we remove those shortcuts as well from default because Cut function is very destructive?

No. The Cut function is either not destructive (e.g., in file managers, nothing happens unless you Paste), or the application has a (hopefully obvious) way to revert the desctruction, like an "Undo" action in the tool bar.

Fri13 wrote:But now the Ctrl+I shortcut is one what can be opened with keyboard but to get it closed quickly with keyboard is tricky.
But we need some useful shortcuts and standard shortcuts globally and per application window.

I fully agree. I am not saying that we should remove any shortcuts. I just tried to make the point that removing the Close button might make it harder to close the filter bar for some users.

colomar wrote:If we combine filter and search in Dolphin, I think it makes sense to have it more permanently.

Filter and search do fundamentally different things, and I do not see any way how they could be merged without breaking some of their respective use cases. This has been discussed already in viewtopic.php?f=285&t=121288

freininghaus wrote:A proposal to make the "Filter Bar" shortcut toggle the visibility of the bar (rather than just show it, as it is currently) is here: https://git.reviewboard.kde.org/r/118719/

The first problem with this approach, which was not obvious at all to me, has been pointed out already: Right now, Ctrl+I focuses the filter bar if it is not focused yet, which is important to at least one user.

I hope that this issue makes it clear why I am so hesitant whenever someone suggests any change, and I try to imagine all possible problems that the change may cause. I'm not doing it because I want to annoy you, but because people use software in many more different ways than we can imagine, and any change, no matter how harmless it looks, can cause problems for some users. IMHO, we have to make sure that the benefits of a suggested change really outweigh these problems before we actually change it.

freininghaus wrote:I hope that this issue makes it clear why I am so hesitant whenever someone suggests any change, and I try to imagine all possible problems that the change may cause. I'm not doing it because I want to annoy you, but because people use software in many more different ways than we can imagine, and any change, no matter how harmless it looks, can cause problems for some users. IMHO, we have to make sure that the benefits of a suggested change really outweigh these problems before we actually change it.

Absolutely! What we find unproductive is if people just say "I like the way it's now and I don't want to change it!". Pointing out potential issues with proposed changes is absolutely crucial. Nobody is perfect. A single person can never think of all possible pitfalls, that's why we discuss things a s a team.

I picked up the ideas from Dolphin in the thread 'New Search in KMail' (viewtopic.php?f=285&t=121598).