Bug 409616

Summary: Custom action on double click on "empty" desktop area
Product: [Plasma] plasmashell Reporter: Marcin Orlowski <mail>
Component: ContainmentAssignee: Sebastian Kügler <sebas>
Status: CONFIRMED ---    
Severity: wishlist CC: kde.podagric, nate, plasma-bugs, xysyfo
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marcin Orlowski 2019-07-08 10:27:47 UTC 
I was using Directory Opus on Windows as general Desktop and file Explorer replacement for years and one of its features I really often miss on KDE now is this - I was able set its desktop that way, that any double click on non icon (basically on "empty" area) triggered an action. I assigned opening new Lister (which is its name for file browser) at the location of mouse pointer. This was really handy and whenever I needed to browse some location I just double clicked the desktop and voila - I had my new file browser opened for the task. It would be then extremely handy to a) be able to start custom app/script on the action b) be able to have action triggered when "just" double clicked on desktop area.
Comment 1 Christoph Feck 2019-07-25 12:39:27 UTC 
The problem is that if you assign an action to a double-click, then the action that you assign to the single-click would either need to be disabled, or it would have to "wait" to see if you actually wanted to double-click, causing an annoying delay for that case.
Comment 2 Nate Graham 2020-01-13 05:49:44 UTC 
That's true, but currently there is no action bound to "single-click on the background." So I don't think that would be a huge problem to disable the ability to set a single-click action if you've set up a double-click action.
Comment 3 Marcin Orlowski 2020-01-13 06:11:04 UTC 
I think this still would be fair trade-off as it's better to have a choice so it's "either A or B" instead "just A", esp. these two should not collide really.
Comment 4 Nate Graham 2020-09-29 15:11:04 UTC 
*** Bug 427090 has been marked as a duplicate of this bug. ***