-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tablet pen map_to_output not applied correctly at startup #5231
Comments
Xyene
added a commit
to Xyene/sway
that referenced
this issue
Apr 20, 2020
Some input rules, like `map_to_output`, are dependent on the presence of a specific screen being present. This currently does not work for hotplugged outputs, or outputs that are processed after the input device is initially probed. This commit fixes both cases, by reconfiguring inputs on each output addition. Fixes swaywm#5231.
Xyene
added a commit
to Xyene/sway
that referenced
this issue
Apr 20, 2020
Some input rules, like `map_to_output`, are dependent on a specific screen being present. This currently does not work for hotplugged outputs, or outputs that are processed after the input device is initially probed. This commit fixes both cases, by reconfiguring inputs on each output addition. Fixes swaywm#5231.
emersion
pushed a commit
that referenced
this issue
Apr 24, 2020
Some input rules, like `map_to_output`, are dependent on a specific screen being present. This currently does not work for hotplugged outputs, or outputs that are processed after the input device is initially probed. This commit fixes both cases, by reconfiguring inputs on each output addition. Fixes #5231.
Xyene
added a commit
to Xyene/sway
that referenced
this issue
Apr 25, 2020
Xyene
added a commit
to Xyene/sway
that referenced
this issue
Apr 25, 2020
Previously in 3de1a39, it "worked by accident" in my testing since the display being used in `map_to_output` was initialized first (the map would not be applied because the display hadn't actually come online yet), and was followed by a second display (at which point the map would get applied for the first display). Refs swaywm#5231
emersion
pushed a commit
that referenced
this issue
Apr 26, 2020
Previously in 3de1a39, it "worked by accident" in my testing since the display being used in `map_to_output` was initialized first (the map would not be applied because the display hadn't actually come online yet), and was followed by a second display (at which point the map would get applied for the first display). Refs #5231
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running sway master, and have two displays, arranged in the below configuration:
(One is 2560x1440, the other 1600x900.)
My sway config contains directives for mapping my pen to
DP-1
.However, on startup, my pen is not confined, and actually appears at the bottom-right corner of
HDMI-A-2
. Moving it over toDP-1
myself doesn't make it confined. Triggering a reload after startup viaswaymsg reload
correctly confines the pen, though.Edit: this appears to me to be a race of sorts. My logs contain:
So, it would seem that if the display isn't initialized before the output map is set, it won't take effect. Seemingly supporting this hypothesis, unplugging and replugging the tablet (rather than
swaymsg reload
) also works.The code responsible is:
sway/sway/input/seat.c
Lines 653 to 658 in 58eb0c4
(
output
isNULL
at that point in time, and the map is never set.)The text was updated successfully, but these errors were encountered: