- Group Reviewers
Clicked on the Icons in the toolbar and menu:
1st click: bar appears
2st click: bar disappears again
3rd: Shortcuts toggle also nice
This comes up a lot, but always runs into opposition because some people like keeping the search (and especially filter) bars open and switching focus to them using a keyboard shortcut. If the keyboard shortcuts also toggle them open and closed, that workflow breaks, and I predict that same complaints will re-emerge.
I'd like this too, in principle, but it seems like we need to figure out a way around this impasse. Thoughts?
Well not really because I can't really imagine what use case this would be and further more when you hit Ctrl + F twice the bar appears again and you can type again. So when anyone know in which situations it would help when the shortcut does not toggle the bar it be great to be enlightened.
My personal use case is:
Hit Ctrl + F
Begin to type to search for files
Hit Ctrl + F again and notice that it not disappear and I have to use the mouse to close it again even it started with a shortcut without any mouse action.
In my book the keyboard shortcut behaviour is perfectly fine right now in Dolphin, and in line with Kate and Firefox: Ctrl+F will always open or focus the search bar, Enter will execute and move focus away, ⎋ will close (needs focus).
Regarding the button: I guess toggling makes more sense. However, your patch is still off here: It only performs the toggling action, but the visual state does not indicate you have opened the search bar (like the Preview button does).
The filter bar indicates the toggle state very nice as it was my plan to be consistent with the preview button ;)
I wanted the same also for the search but was not able to figure it out until then.
Will take another look at this.
And don't know if I will be able to achive the suggested solution but I will try my best.
Okay I don't know what to do now. I wanted to add a new setting to dolphins general settings menu -> no problem at all.
Then I wanted to extend the find() and showfilterbar() function with an optional parameter so that I would be able to set them active then the shortcut was used (and the option off which would be the default) or toggle them when the button in the toolbar or menu was clicked.
First I tried to extend the connect() call with this parameter but I noticed that this is not so easy possible and then I tought "Is this the right way at all? This will not help at all because the signal will be forwarded anyway if the shortcut was pressed or the button was clicked ..."
My next idea was to make a new Action out of it but I don't want to have two actions in the menus and furthermore the shortcut could only handle one of it which would be really weird and confusing.
And so I am sticked and searching for a way to find out if the call from find() or showfilterbar() was made trough a button or the shortcut to make this different behavior possible. Any ideas?