Bug 480708

Summary:	Virtual desktop switch on screen borders + mouse wheel
Product:	[Plasma] kwin	Reporter:	bousket
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	fanzhuyifan, nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description bousket 2024-02-01 22:13:01 UTC

SUMMARY
***
In order to switch desktop with mouse only, I d like to add the following behavior:
When mouse is on the vertical screen edges, mouse wheel switches desktop.
***

ADDITIONAL INFORMATION
Current desktop switch with mouse wheel on (empty part of) desktop don't work if there is a maximized window on the desktop (because the maximized window gets the scroll).
This leads to inconsistent behavior (work on empty desktop and doesn't on other with maximized window).
This idea makes desktop switching behavior consistent and convenient (with mouse only, no need of meta or ctrl+alt).
Thanks for reading.
Sorry if I made some mistakes on required fields.

Comment 1 fanzhuyifan 2024-02-01 23:29:36 UTC

Thank you for your bug report!

Unfortunately I don't think this feature, as proposed, would be very useful. It is impossible to position your cursor exactly on the edge -- you are either on one screen or the other.

As a workaround, you could consider putting a pager in your panel, and you could scroll on the pager to switch desktops.

Comment 2 bousket 2024-02-01 23:38:11 UTC

There are currently settings for screen edges.
Can't we use these edges to implement desktop switching with mouse wheel ?

Actually, this feature was already there in kde 3 and it disappeared later.

Comment 3 Nate Graham 2024-02-06 22:47:05 UTC

You can position your cursor exactly on an edge if there's no other screen on the other side of that edge. So the proposed feature would work in that case.

I think this is probably going to be one of those "Patches welcome" features that nobody on the KWin dev team is likely to bject to, but they are equally unlikely to implement it themselves. :)