You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
When using 0.10.0-216-g6c8f66ff59b2 ("xcursor: add xorg-x11 and cursors path to XCURSORPATH") against Sway 1.5-rc1-2-gbb85b9070d05 ("tree/view: fix smart borders with tabbed/stacked ancestor") on a non-atomic-modesetting-enabled machine, an swaymsg output 0 dpms on is unable to restore the monitor back from DPMS sleep previously entered into by means of swaymsg output 0 dpms off. Only switching to another VT and back achieves the desired effect.
Testing 15d8f18 (cc @emersion) against Sway 1.2-rc1-372-g6f7b548589fe ("ipc: invert output transformation when necessary") revealed that the cause is the following(1) undocumented semantical bit:
When using 0.10.0-216-g6c8f66ff59b2 ("xcursor: add xorg-x11 and cursors path to XCURSORPATH") against Sway 1.5-rc1-2-gbb85b9070d05 ("tree/view: fix smart borders with tabbed/stacked ancestor") on a non-atomic-modesetting-enabled machine, an
swaymsg output 0 dpms on
is unable to restore the monitor back from DPMS sleep previously entered into by means ofswaymsg output 0 dpms off
. Only switching to another VT and back achieves the desired effect.Testing 15d8f18 (cc @emersion) against Sway 1.2-rc1-372-g6f7b548589fe ("ipc: invert output transformation when necessary") revealed that the cause is the following(1) undocumented semantical bit:
instead of the purely syntactical
A quickly testable version is here (without pretending that its description is too insightful).
The text was updated successfully, but these errors were encountered: