https://bugs.kde.org/show_bug.cgi?id=428760

Jerrod Frost <piroisl...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|Neon Packages               |Manjaro
          Component|kded                        |input
            Product|KScreen                     |kwin
   Target Milestone|---                         |5
           Assignee|kscreen-bugs-n...@kde.org   |kwin-bugs-n...@kde.org
            Version|5.20.2                      |5.23.5
                 CC|                            |piroisl...@gmail.com

--- Comment #2 from Jerrod Frost <piroisl...@gmail.com> ---
I too have this issue and its bigger than kscreen alone as Wayland greatly
alters the situation. This is occurring on more than just laptops and drawing
tablets, but production machines as well.

Scenario:
I run a livestream broadcasting station for a small church of about 100 people
and we livestream broadcast to Facebook and Youtube. I run a station of about 4
monitors. 2 are for OBS (1 streaming, 1 Preview which is split off and
presented on TVs all around the church), 2 of these monitors are 12"
touchscreen monitors set to 1366x768 and are used to control a BlackMagic TV
Studio ATEM for camera switching and the other is used to control a
Behringer-X32 Soundboard for Livestream Volume control across 32 channels.
We've had other churches contacting us from all over asking how we're doing all
this and we've invited them over to look, learn, and replicate. So this
scenario will likely grow drastically over time.

These touch screens attempt to act as a touch interface for ALL 4 MONITORS. I
have to lock them to their respective monitors with the command "xinput
--map-to-output {xinput device ID} {xrandr ouput ID}" every time I boot up the
computer. While this isn't ideal, it is a doable solution. The problem is, when
using wayland/xwayland, this solution is gone. xinput list is masked and you
are presented with "xwayland-pointer, xwayland-related-pointer, and
xwayland-touch". You no longer have individual device IDs to link multiple or
any touch screens to specific outputs. You're now stuck with every touchscreen
attempting to control ALL 4 SCREENS unless you revert to X11.

There needs to be method to link inputs to specific outputs even under wayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to