20
849
Fork
You've already forked fuzzel
83

Issue with corners rendering #90

Closed
opened 2022年01月13日 15:59:21 +01:00 by flipflop133 · 4 comments

I noticed that when you launch Fuzzel, corners are well rendered, but when you start navigating through elements it gets badly rendered like if rendering was applied over the old one without cleaning the previous one.
I attached two screenshots so you can compare the two.
EDIT: just noticed this issue is present on the showcase screenshot on the Fuzzel git home page so I guess you are aware of it and reason is that you don't want to waste ressources in such rendering I guess.

I noticed that when you launch Fuzzel, corners are well rendered, but when you start navigating through elements it gets badly rendered like if rendering was applied over the old one without cleaning the previous one. I attached two screenshots so you can compare the two. EDIT: just noticed this issue is present on the showcase screenshot on the Fuzzel git home page so I guess you are aware of it and reason is that you don't want to waste ressources in such rendering I guess.
Owner
Copy link

Can you share your fuzzel options?

Can you share your fuzzel options?
Owner
Copy link

EDIT: just noticed this issue is present on the showcase screenshot on the Fuzzel git home page so I guess you are aware of it and reason is that you don't want to waste ressources in such rendering I guess.

Nope - I don't use rounded corners myself, and was probably busy looking at other details when doing the screenshot...

> EDIT: just noticed this issue is present on the showcase screenshot on the Fuzzel git home page so I guess you are aware of it and reason is that you don't want to waste ressources in such rendering I guess. Nope - I don't use rounded corners myself, and was probably busy looking at other details when doing the screenshot...
Owner
Copy link

The effect was hard to see against a black/dark background, but once I tested against a white background, it was easy to spot with the default options.

#91 should fix this.

The effect was hard to see against a black/dark background, but once I tested against a white background, it was easy to spot with the default options. https://codeberg.org/dnkl/fuzzel/pulls/91 should fix this.

Thanks for the quick fix, really appreciate your work!

Thanks for the quick fix, really appreciate your work!
Sign in to join this conversation.
No Branch/Tag specified
master
gnome-support
releases/1.14
issue-319-window-switching
issue-561-nord-theme-only
resvg-filtering-take-2
resvg-filtering
releases/1.13
rehanzo-dont-ignore-execute-648
keybinds-overwrite
issue-561-refresh-theme
ci-automated-testing
reenable-legacy-icons
releases/1.12
test-coverage-for-fzf-caching
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.2
1.4.1
1.4.0
1.3.0
1.2.0
1.1.0
1.0.1
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fuzzel#90
Reference in a new issue
dnkl/fuzzel
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?