-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add GenericIcon #936
Add GenericIcon #936
Conversation
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #936 +/- ##
==========================================
- Coverage 55.81% 55.58% -0.23%
==========================================
Files 616 618 +2
Lines 19724 19844 +120
Branches 1518 1529 +11
==========================================
+ Hits 11008 11031 +23
- Misses 8374 8464 +90
- Partials 342 349 +7
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.
As discussed in call:
- Add
Size
attribute to manage both Height/Width and FontSize in a unified way. - Make sure Size works for all of them, add Stretch if necessary etc.
- Add
GenericIconStyles
and add the examples there, use Classes inGenericIcon.axaml
For the record: <local:GenericIcon SvgPath="avares://NexusMods.App.UI/Assets/Icons/add_circle_24px.svg"/> as opposed to how you currently have to do it in the PR: <local:GenericIcon>
<local:GenericIcon.Value>
<local:IconValue>
<local:IconValue.AvaloniaSvgSetter>
<local:AvaloniaSvg Path="avares://NexusMods.App.UI/Assets/Icons/add_circle_24px.svg"/>
</local:IconValue.AvaloniaSvgSetter>
</local:IconValue>
</local:GenericIcon.Value>
</local:GenericIcon> , which would be hidden inside a Style Class. The argument against from @erri120 was that this would defeat the purpose of having a unified Api, as it would be possible to OneWayBind to the other setter properties as well, ending up with different ways the control can be interacted with. I still would have liked the convenience, regardless. We agreed to disagree. |
Resolves #934.