diff options
| author | srdusr <[email protected]> | 2025-11-15 14:51:00 +0200 |
|---|---|---|
| committer | srdusr <[email protected]> | 2025-11-15 14:51:00 +0200 |
| commit | 16950c4cfc13bbffad07254f0d994d10a1a88774 (patch) | |
| tree | 06cad298c85fe6c5570037fc57c8650b0aa46b32 /docs/DEFAULTS.md | |
| parent | f988203a7c22d945383efa9609f5c8a09a9506d2 (diff) | |
| download | srdwm-16950c4cfc13bbffad07254f0d994d10a1a88774.tar.gz srdwm-16950c4cfc13bbffad07254f0d994d10a1a88774.zip | |
Document why monitor scale stays config-only, park the disable/re-enable question
Investigated a live srd.monitor.scale path, the obvious next candidate
after monitor.split's own live path. Unlike split (a pure
placement computation), scale is only ever read by disable_connector_by_
name/enable_connector_by_name - applying it live means a real disable-
then-re-enable cycle on the physical connector, the same screen blank a
genuine unplug/replug causes. Parked the "is that an acceptable cost"
question rather than deciding it alone; left monitor.scale as Lua-
config/restart-only for now.
Diffstat (limited to 'docs/DEFAULTS.md')
0 files changed, 0 insertions, 0 deletions