You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to do this, you'd have to do the same thing as the Shape implementation for RoundedRect does, with the exception that each corner could have a different radius (or none). It would also make it much easier to implement styling of all corners in druid.
The overhead on RoundedRect would be minimal. This could easily be implemented by making RoundedRectPathIter::arcsOption<T>s and adding three more f64 for each corner in RoundedRect. I'm not sure how a non-rounded corner (ie. zero radius) should be specified. Two possibilities are making the radius variables in RoundedRect also Option or when creating the RoundedRectPathIter comparing the radius to some minimum value.
I will implement this if I get the Ok and some feedback on the problem I mentioned.
The text was updated successfully, but these errors were encountered:
Just dropping by. It seems that kurbo still lacks the elliptically rounded rectangles, which flutter supports. Basically we just need to use two parameters per corner (radius_X, radius_Y) to describe the rounding radius. Note that this cannot be emulated by an affine transform on existing RoundedRect, since the four corners may use wildly different ellipses.
I haven't really encountered anything significant in Flutter that uses this feature. But this is concerning when trying to emulate Flutter.
Unfortunately, if this is implemented on current RoundedRect, it will be a breaking (?) change. Or we could add a second type (though the name could probably be mouthful). Or we could choose to not implement. If the decision is to implement, I can take time to investigate.
Currently, to do this, you'd have to do the same thing as the
Shape
implementation forRoundedRect
does, with the exception that each corner could have a different radius (or none). It would also make it much easier to implement styling of all corners indruid
.The overhead on
RoundedRect
would be minimal. This could easily be implemented by makingRoundedRectPathIter::arcs
Option<T>
s and adding three moref64
for each corner inRoundedRect
. I'm not sure how a non-rounded corner (ie. zero radius) should be specified. Two possibilities are making the radius variables inRoundedRect
alsoOption
or when creating theRoundedRectPathIter
comparing the radius to some minimum value.I will implement this if I get the Ok and some feedback on the problem I mentioned.
The text was updated successfully, but these errors were encountered: