-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Fix case where h_separation
might not work in Button
#64218
Fix case where h_separation
might not work in Button
#64218
Conversation
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.
Looks good.
a6a4220
to
bf9162b
Compare
You added me as co-author (GitHub does this automatically when you accept a suggestion). |
bf9162b
to
bebc75e
Compare
bebc75e
to
8f54e69
Compare
Sorry, |
Uh why should it be ignored? It's just a space between icon and text. If you expand icon and resize to 0, it's still there and separation should take effect. The previous behavior was alright. |
For Button-derived classes with internal elements, Of course, they behave inconsistently, and it's not clear to me which one to use as a standard. |
d31d053
to
323d611
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
323d611
to
ec66f7c
Compare
This patch mainly solves two things: 1. The typo of `h_separation`; 2. Negative values of `h_separation` will be treated as `0` when used, to prevent the button's minimum `width` from being reduced by `h_separation`.
ec66f7c
to
4a3a15c
Compare
I seem to be getting more and more deviated from the original intention. Now I only fix typo and restrict When |
I guess it has something to do with
Currently, changes in the factors that affect
This should be a drawing issue, which will be resolved in #64351, where there is a set of comparison images with alpha13. |
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.
I assume #64218 (comment) is addressed in #64351?
I guess no, both patches are trying to get back to alpha13. Except that a negative This issue in #64218 (comment) also exists in alpha13. I'm a little unclear on what exactly it should look like. So had to use alpha13 as a reference. If there is something wrong in alpha13, I will fix it later. I'm a little concerned about over-modification causing other regressions. It might be better to figure out what it should look like first.
The above will directly and indirectly affect the minimum size.
I haven't looked into the button's design criteria, so I'm a little confused. However, this patch is intended to fix typo to get it back to a slightly better state. |
Thanks! |
Fix #64140.
Bugsquad edit: Fixes #64371
Split from #59340.There are still issues with the drawing and will be fixed in another PR.
Edit:
This patch mainly solves two things:
h_separation
;h_separation
will be treated as0
when used, to prevent the button's minimumwidth
from being reduced byh_separation
.