https://bugs.kde.org/show_bug.cgi?id=482865
ngoonee.t...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Ever confirmed|1 |0
Status|RESOLVED |REPORTED
--- Comment #6 from ngoonee.t...@gmail.com ---
(In reply to Zamundaaa from comment #5)
> Git commit 354a71855e04ee28311410e1b6d2a69cddcbcdbc by Xaver Hugl.
> Committed on 29/04/2024 at 14:13.
> Pushed by zamundaaa into branch 'master'.
>
> workspace: unify active screen modes
>
> Instead of the active screen being purely defined by the mouse position,
> or purely defined by the active window and keyboard shortcuts, this changes
> it to make the active screen all about the last user interaction. This should
> work for most workflows without needing a setting to choose between two
> flawed
> approaches.
> Related: bug 484902, bug 484902
>
> M +0 -3 src/kwin.kcfg
> M +2 -0 src/main_x11.cpp
> M +0 -11 src/options.cpp
> M +0 -9 src/options.h
> M +1 -1 src/pointer_input.cpp
> M +1 -1 src/tablet_input.cpp
> M +1 -1 src/touch_input.cpp
> M +7 -34 src/useractions.cpp
> M +0 -31 src/workspace.cpp
> M +0 -3 src/workspace.h
>
> https://invent.kde.org/plasma/kwin/-/commit/
> 354a71855e04ee28311410e1b6d2a69cddcbcdbc
Not entirely sure whether/how this would solve the use case for using keyboards
to change the active screen, but it would certainly fix the other oddity I've
noticed with my graphics tablet, that it would randomly 'choose' a monitor and
work based on that monitor rather than following the 'active screen'. Moving
the mouse over, interacting with windows on the 'other' screen, would not
change the graphics tablet focus.
--
You are receiving this mail because:
You are watching all bug changes.
