Bug 135097

Summary:	Mouse Trails when using Mouse Gestures
Product:	[Applications] systemsettings	Reporter:	Hans Chen <hanswchen>
Component:	kcm_khotkeys	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	MurzNN, qydwhotmail, witchhunterpro
Priority:	NOR
Version:	5.22.0
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	A screenshot of mouse trails Sorry, I had the wrong tab opened in the first screenshot. Here are the different options

Description Hans Chen 2006-10-04 16:52:37 UTC

Version:           2.1 (using KDE KDE 3.5.4)
Installed from:    Slackware Packages
OS:                Linux

If you use for example Firefox' "Mouse Gestures" extension you know that you can enable Mouse Trails. Then the mouse pointer will leave a trace if you are holding down the mouse button.

I think this option is very nice, as you can actually see the gesture you're drawing (and you are get ting a 'feedback'). However, I don't think it should be enabled as default.

There are some options too, which are:

Trail width
Dot interval
Color
Opacity
Stop drawing after:

Comment 1 Hans Chen 2006-10-04 17:01:39 UTC

Created attachment 18011 [details]
A screenshot of mouse trails

Comment 2 Hans Chen 2006-10-04 17:06:59 UTC

Created attachment 18012 [details]
Sorry, I had the wrong tab opened in the first screenshot. Here are the different options

Comment 3 Benno Dielmann 2008-07-20 11:54:09 UTC

Could probably use techniques from the Mouse Mark KWin plugin... :-)

Comment 4 Christoph Feck 2013-11-19 00:53:02 UTC

*** Bug 327750 has been marked as a duplicate of this bug. ***

Comment 5 Murz 2021-05-05 12:55:22 UTC

*** Bug 399304 has been marked as a duplicate of this bug. ***

Comment 6 Fushan Wen 2021-05-06 10:00:52 UTC

*** This bug has been confirmed by popular vote. ***

Comment 7 witchhunter 2021-07-29 19:17:55 UTC

Just checked "Mouse Mark" desktop effect and it works on X11 and Wayland, with no CPU/GPU penalties whatsoever.

Comment 8 Fushan Wen 2021-11-03 14:18:30 UTC

An option is to create an transparent full-screen window when drawing a gesture.
Another option is to port khotkeys to kwin's module, which could even make gesture work under Wayland.

Comment 9 witchhunter 2022-01-02 17:57:46 UTC

(In reply to Fushan Wen from comment #8)
> An option is to create an transparent full-screen window when drawing a
> gesture.
> Another option is to port khotkeys to kwin's module, which could even make
> gesture work under Wayland.

As a matter of fact I was thinking doing the same thing with some scripting, regarding the first option, which turns out impossible without C++ dive in, so no go for me. The main obstacle here would be registering mouse trigger sequence. So IMHO, the latter option would be preferable   (especially considering different mouse keys as a trigger above different windows, but that is a whole other topic).

For the record, this is way more notable feature then touchpad gestures in every single aspect (and in all my ignorance, maybe even groundbreaking for latter tablet implementation).

Comment 10 Nate Graham 2024-03-04 19:41:57 UTC

As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now.

Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again.

Thanks for your understanding, everyone.