Skip to content

The scale docs say what a zone is told, and what auto gives back - #643

Open
DevomB wants to merge 1 commit into
mainfrom
scale-docs-fractional
Open

DevomB wants to merge 1 commit into
mainfrom
scale-docs-fractional

Conversation

@DevomB

@DevomB DevomB commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Based on main (ea27351). Docs and one usage text; no build input changes.

What was stale.

  • docs/user-guide.md (Monitors) and docs/design/laptop.md said zones are told the scale "rounded up to a whole number, and draw that much larger".
  • Since A zone's window hears the scale it is shown at, so the browser draws text sharp at 1.5 #520, the proxy passes wp_fractional_scale_manager_v1 (compositor/wlproxy/src/policy.rs:21). A zone's window is told the exact scale, and Firefox draws sharp at it.
  • Kryptik's own windows do not follow the scale. havoc (the chrome's menu and every terminal) and kryptik-lock draw at 1 and are enlarged by the compositor, so at any scale but 1 they look soft. The guide suggested 1.5 without saying so.
  • kryptik display NAME auto deletes that monitor's line (tools/kryptik:505-507). kryptik-display.c:370-389 then gives the * line if there is one, and only otherwise 2 for a built-in panel of 192 dpi and 1200 lines or more. The guide and the command's usage gave only the built-in rule, without the 1200 lines.

What changes. The guide's Monitors paragraph, laptop.md's scale paragraph and the display NAME auto usage lines in tools/kryptik now say the above.

From the ZBook desktop audit, where two refuters checked it against the code.

Tests. bash -n tools/kryptik. Nothing else runs docs.

Since the proxy passes wp_fractional_scale_v1, a zone's window is told the
exact scale, and the browser draws sharp at it. The user guide and laptop.md
still said zones hear a whole number, rounded up. havoc and the lock draw at
1 and are enlarged, so they look soft at any scale but 1, which the guide
now says beside its suggestion of 1.5. `kryptik display NAME auto` drops the
monitor's line, so a `*` line wins over the built-in rule, which also needs
1200 lines; the guide and the command's usage now say both.
DevomB added a commit that referenced this pull request Oct 23, 2026
@DevomB
DevomB marked this pull request as ready for review October 23, 2026 12:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant