https://bugs.kde.org/show_bug.cgi?id=524672
Bug ID: 524672
Summary: feature: Add window rules for Controller
Keyboard/Mouse functionality and Touchpad device
activation
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: input
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
I frequently use my Sony DualSense Wireless Controller when I play (usually
emulated) games, due to its touchpad providing many intuitive and fast ways to
interface with a given emulated system. But using it at any given setting isn't
a once size fits all ordeal.
For instance (although convenient when outside of gameplay for navigational
purposes), when Controller Keyboard/Mouse functionality is Enabled, I have to
input new button mappings because of their reassignment to keyboard presses.
This can also result in issues where controller inputs that would perform a
certain action in a dashboard/paused emulation state perform other actions
because said actions are mapped to keyboard keys.
On a similar note, having the touchpad being bound to the mouse at all times
can be a double-edged sword in certain emulated system implementations.
Take for example using it to input presses on a Nintendo DS's touchscreen. On
some emulators you are given a color inverted pixel to show where your
hypothetical "stylus" is positioned, but others do not have that functionality
at all leaving one without any visual indication of where they are pressing
until one presses something interactable.
When the mouse pointer is active in the former, you have a cursor flying around
the screen as you try to play distracting you. But if it isn't active in the
latter, you have no idea where you may be touching at any given point.
And on the Wii, not only do games already have a cursor already as a necessity,
but if you bind the XY position of your touch on the pad directly to the
screenspace while the touchpad mouse functionality is active the entire
function breaks. Only after disabling the touchpad does the intended mapping
work properly. Yes, I've made sure to double and triple check any variables
that would make sense to check, it just doesn't work when the touchpad is
controlling the mouse as well.
Making these two options window rule variables would be a convenient way to
solve both of these problems, I believe. If such functionality already exists,
I wouldn't even know where to start implementing it fluidly and seamlessly.
Thank you for your time and consideration.
--
You are receiving this mail because:
You are watching all bug changes.
