Repository navigation
Conversation
The composer's amber halo and the shadows of dialogs and menus were four translucent rounded rectangles, each 3 px larger than the last, standing in for a blur: their edges showed as steps, and the halo ended on a visible line. Each is now one picture drawn at the screen's resolution, fading out as a blurred shape does (a Gaussian edge), as dark as before at the edge. The halo sits over the composer's shadow, which hid it on the sides, so it is now even all around and a little brighter. The subchat tree's bend was four short Fyne lines, each end rounded to the pixel: lumpy, as the usage chart's lines were (#445). The guide is now drawn as one picture: its straight parts on whole pixels, crisp, its bend a smooth quarter circle. Rasters are sized to whole pixels and drawn with nearest sampling: Fyne placed them at fractional positions and smoothed them, spreading each crisp line over two rows; the usage chart's strokes get the same treatment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assisted-by: Claude Opus 5.5 medium
The bend was drawn 0.8 px wider than the straight parts so that it would not look fainter: it overhung them where they meet, a dark speck at the corner, and looked heavier than the rest. It is now exactly as wide, so its edges carry on the line's, like the app's other rounded corners. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assisted-by: Claude Opus 5.5 medium
tpm28
marked this pull request as ready for review
November 16, 2026 16:18
Member
|
Heads-up from testing the open PRs merged together: this PR and #472 both change |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendering that looked rough at the pixel level: the composer's amber halo, the shadows of dialogs and menus, and the subchat tree's line.
What was wrong
What changes
soft_shadow.go), fading out like a blurred shape. A Gaussian edge, cached per size, takes about 2 ms for a large dialog. Near its edge a shadow is as dark as before; inside, it is unchanged.Tested
gofmt,go vet ./..., wasm vet,go test ./...; the UI tests ran 3 times.Linux, 1.4×
Halo, before (left) and after (right):

Menu shadow corner, before and after:

Subchat tree, before and after:

Windows, 1×
Halo, before and after:

Subchat tree, before and after:

Dialog shadow corner, before and after:

Search dialog: the frosted backdrop is kept.

Not checked by eye: the subscription limits chart, because there is no limits data in the test profiles (its tests pass), and the light theme.
Assisted-by: Claude Opus 5.5 medium
🤖 Generated with Claude Code