docs: record Parent Call, the DVD migration and what is left to test
Three things in this window that a container cannot answer, and they are now the top of the next-steps list: a real key pressed into Parent Call, a television switched on after the computer, and a disc that plays. Also brings the comments in the shared libraries up to date. The only mention of sway left in the tree is the upgrade step that removes the sway-era login shell from a room being upgraded. Co-Authored-By: Claude Opus 5 <[email protected]>
This commit is contained in:
co-authored by
Claude Opus 5
parent
e8078e37c1
commit
13aac85b87
@@ -1,13 +1,14 @@
|
||||
"""Icons that stay sharp when the compositor scales the session.
|
||||
|
||||
new_from_file_at_scale rasterises an SVG at its *logical* size. Under
|
||||
sway's output scaling the compositor then enlarges that finished raster,
|
||||
output scaling the compositor then enlarges that finished raster,
|
||||
which is why icons went soft while the clock text and the dock surface
|
||||
stayed crisp: those are drawn by GTK at the display's real pixel
|
||||
density, and the icon was not.
|
||||
|
||||
GTK 3 has no fractional scaling, so sway advertises the ceiling integer
|
||||
scale and scales the finished buffer down. Measured under sway: scale
|
||||
GTK 3 has no fractional scaling, so the compositor advertises the ceiling
|
||||
integer
|
||||
scale and scales the finished buffer down. Measured: scale
|
||||
factor 1 at output scale 1.0, and 2 at 1.25, 1.5 and 2.0.
|
||||
|
||||
So the fix is to rasterise at size * scale_factor physical pixels and
|
||||
|
||||
Reference in New Issue
Block a user