-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layoutbox rendering is blurry on HiDPI screen #3790
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3790 +/- ##
=======================================
Coverage 90.99% 91.00%
=======================================
Files 900 900
Lines 57502 57505 +3
=======================================
+ Hits 52326 52330 +4
+ Misses 5176 5175 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late replies on your PRs.
I have this idea to move all the awful.widget.*
widgets to template, so that the user can define the consumer widget with whatever they want.
Regardless, this fix is more than welcome! And I don't think it would clash with my targets, since we need to preserve a default widget that is backward compatible with the current usage.
So it's all good to me. Thank you!
Sorry for my even longer delay before taking a look at this. It looks good, but to be merged the CI warning needs to be fixed: Checking lib/awful/widget/launcher.lua OK
Checking lib/awful/widget/layoutbox.lua 1 warning
lib/awful/widget/layoutbox.lua:18:7: unused variable 'surface' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
@Mergifyio refresh |
✅ Pull request refreshed |
I think, layoutbox should not render icons directly. On HiDPI screens, svg files rendered this way are always in base resoltuion, which looks blurry. Method :set_image() should be called instead.
Few possible modifications:
Silent loading (surface.load_silently) could be dropped and if "layout_" .. name is set, image can be loaded directly. If it's not set, user will see just text representation. If path to image is not valid, i think, it's ok to display error message.
Or imagebox could have interface for silent loading.