Bug 411713

Summary: Option to increase text and icons size to improve visual feedback.
Product: [Plasma] krunner Reporter: leftcrane <leftcrane>
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: alexander.lohnau
Priority: NOR    
Version: 5.15.90   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description leftcrane 2019-09-08 13:20:50 UTC 
The default text/icon/row sizes are quite small and thus may not provide adequate visual feedback and sufficiently large click targets. 

KRunner, especially with a bunch of plugins enabled isn't a launcher that you can use blindly because the results are too often not what you expect. This makes it important to have taller row sizes, so the user can easily see what they are about to launch or use the mouse to select a result that is too far away to be reached with the arrow key. This would also be important for touch.

If you look at other launchers like Quicksilver or Ulauncher, the text and icon sizes are much bigger. This improves visual feedback.


Proposal:

- Add some option to configure icon size and text size:
- Consider making the items bigger by default and increase the padding.
Comment 1 Kai Uwe Broulik 2019-09-08 14:18:54 UTC 
Have you looked at macOS spotlight? It has literally the same font size and delegate size as we have.
Comment 2 leftcrane 2019-09-08 20:26:09 UTC 
Hmm, I guess you're right. But it does have a huge preview pane and input box, which helps with visual feedback. Also Spotlight reads your intention much better than Krunner, so the first result is typically what you want.

Aren't the icons bigger in Spotlight though? I don't think they are 16 px or are they?
Comment 3 leftcrane 2019-09-08 20:28:25 UTC 
Increasing the font/icons/padding would be an intermediate measure - there are better ways to improve usability with a more comprehensive redesign.
Comment 4 Alexander Lohnau 2020-06-28 05:12:47 UTC 

*** This bug has been marked as a duplicate of bug 422567 ***