Bug 375207

Summary: bring back the historylist (downarrow) for better mouse (keyboardless) usability
Product: [Plasma] krunner Reporter: alt.bo-btg0tjq
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: CLOSED FIXED    
Severity: wishlist CC: firefox, fox, nate
Priority: NOR Keywords: usability
Version: 5.8.2Flags: firefox: Usability+
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In: 5.13.0 then reappeared in 5.14.3
Sentry Crash Report:
Attachments: how it used to look - this is proper
screenshot of current version - no mouse support !

Description alt.bo-btg0tjq 2017-01-17 23:56:17 UTC
Since the downarrow-historylist was removed, usability suffered.

With the downarrow to click, one could re-run an old entry, such as "kdesudo dolphin" without letting go of the mouse. 

Without that downarrow-button to click with the mouse, one is forced to leave mouse, hit "K" on the keyboard, then return to mouse to launch the command. Continuous mouse-operation, without use of the keyboard, is more desirable and faster, and was possible before.

This mode of op. is significantly worse, in terms of usability, than in older versions of krunner.

There seems to be no advantage in removing the downarrow-button.

https://userbase.kde.org/Plasma/Krunner currently shows the screenshot from the good old days, with downarrow button to the left of the "?"-button. Maybe downversioninng of krunner will help to get it back.
Comment 1 fox 2017-04-22 07:14:18 UTC
I concur. The history-list via downarrow is essential for good ergonomy of the K DE.

We cannot force the mouse people to use the keyboard when it is not necessary.

A huge loss in productivity !
Comment 2 fox 2017-04-22 07:48:36 UTC
Created attachment 105146 [details]
how it used to look - this is proper

screenshot of proper Krunner
Comment 3 fox 2017-04-22 07:50:49 UTC
Created attachment 105147 [details]
screenshot of current version - no mouse support !

The new current version has no clickable down-arrow anymore, forces user to change to keyboard. Poor productivity, usability suffers !
Comment 4 fox 2018-02-19 02:29:42 UTC
it is so terrible.


krunner is next to worthless without the arrow.


an when will they stop enabling 1 billion plugin for krunner? it slows down the whole computer!!
Comment 5 Kai Uwe Broulik 2018-02-19 10:08:19 UTC
Just press the down arrow when KRunner is opened.

I agree that there should be a visual cue for that. I'll see if I can put an arrow in there.
Comment 6 fox 2018-02-19 12:39:55 UTC
It is not about the cue - it is about having your right hand to leave the mouse to hit the fucking arrow-key on the keyboard - then go back to mouse after a single fucking operation -  or do it via a mouseclick in the fucking first place.


huge difference , my friend. greetz out to KDE
Comment 7 Nate Graham 2018-02-19 14:06:11 UTC
fox@ffoxfire.33mail.com, obscenity is unwarranted. Please be respectful of the people who are providing you with world-class software at no cost, and read https://www.kde.org/code-of-conduct/

As Kai mentioned, he's looking into a patch to re-add it, In fact, here is that patch: https://phabricator.kde.org/D10652
Comment 8 Kai Uwe Broulik 2018-02-19 14:09:38 UTC
Git commit 8227e4e2b7f034166cbf5efb01e4e715028b4606 by Kai Uwe Broulik.
Committed on 19/02/2018 at 14:09.
Pushed by broulik into branch 'master'.

[Run Command] Add history drop down button

Indicates that there's a "drop down" history similar to a ComboBox.
The fact that you can press the down arrow to bring it up is hardly discoverable.
FIXED-IN: 5.13.0

Differential Revision: https://phabricator.kde.org/D10652

M  +29   -0    lookandfeel/contents/runcommand/RunCommand.qml

https://commits.kde.org/plasma-workspace/8227e4e2b7f034166cbf5efb01e4e715028b4606
Comment 9 Kai Uwe Broulik 2018-02-19 14:13:14 UTC
By "a visual cue" I actually meant a button that you can click on, sorry for the confusion.
Comment 10 fox 2018-02-19 22:56:29 UTC
wow, thannk You. can't wait to update my rolling release.
Comment 11 fire f. 2018-04-22 15:43:47 UTC
the feature is not yet in KDE neon live CDROM. why not ?
Comment 12 Nate Graham 2018-04-22 15:48:04 UTC
That would be a question for the Neon packagers.
Comment 13 Christoph Feck 2018-04-24 01:20:54 UTC
This ticket is fixed in Plasma 5.13.0, which is not released yet. If you want to test the change, try KDE neon dev unstable.
Comment 14 fire f. 2018-11-13 05:19:43 UTC
(In reply to Christoph Feck from comment #13)
> This ticket is fixed in Plasma 5.13.0, which is not released yet. If you
> want to test the change, try KDE neon dev unstable.

Excactly as I predicted, in Plasma 5.14.3 , current in rolling rel. Manjaro, the down-arrow is gone away again. 

Back to the old bad unergonomic situation.
Comment 15 fire f. 2018-11-13 05:44:20 UTC
(In reply to fire f. from comment #14)
> (In reply to Christoph Feck from comment #13)
 
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/runcommand/RunCommand.qml


these .qml files change over the vearous themes like "breeze" , "oxygen", etc. 
concerning  history-list. Should they not be the same ?


qmlviewer-qt4 .⁄RunCommand.qml 

to see a bunch of errors as usual.
Comment 16 fire f. 2018-11-13 06:15:07 UTC
seemingly the current master/tree version works.

I removed the .qml manually and put the master version in its place.

relogin, verified Alt-F2 does nothing without the .qml , then copyied the right .qml, and the down-arrow was back like it should be.

6 changes were made, maybe some intermediate version is not well.


this one works:

https://cgit.kde.org/plasma-workspace.git/plain/lookandfeel/contents/runcommand/RunCommand.qml?id=8227e4e2b7f034166cbf5efb01e4e715028b4606


save in raw mode to /usr/....   to have the arrow back in place.
Comment 17 fire f. 2018-11-13 06:18:26 UTC
assuming the distros will get a correct version anytime soon, the bug report may be closed again, I presume. Please recheck, though. Thx!
Comment 18 Nate Graham 2018-11-15 04:15:16 UTC
I see the down arrow in Manjaro with Plasma 5.14.3. If it's still not working for you, it's not a problem in the code and you might want to investigate whether a local misconfiguration is at play or take it up with the distro maintainers.