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
Due to how Paths work in Flutter and Skia, the DashedLine widget takes NOT as much space as the dashed line needs, but as much it needs to contain all the control points.
This suggests that this is a limit of the Flutter rendering engine while it is obviously not. You are free to define the size of your render objects however you please.
Implementation
I assume you are using Path.getBounds for the bounds of your DashedLine widget (I have not looked into the implementation).
This, of course, returns the control points. I am not sure if Path.computeMetrics makes figuring out the actual visible bounds any easier, but you can always calculate it yourself if the existing implementation does not provide it for you.
This is clearly possible and probably also fairly trivial (considering the existing work on bezier curves et al.)
The text was updated successfully, but these errors were encountered:
First up, this is a really cool package! Thanks for creating it ❤️
Use case
It would be useful if the
DashedLine
widget was the same size as the visible dashed line instead of the size of the control points.Proposal
Add option to the
DashedLine
widget to take up the size that the displayed path will take up.Current note
I am aware of the note you added to your README, however, I actually think it is somewhat misleading:
This suggests that this is a limit of the Flutter rendering engine while it is obviously not. You are free to define the size of your render objects however you please.
Implementation
I assume you are using
Path.getBounds
for the bounds of yourDashedLine
widget (I have not looked into the implementation).This, of course, returns the control points. I am not sure if
Path.computeMetrics
makes figuring out the actual visible bounds any easier, but you can always calculate it yourself if the existing implementation does not provide it for you.This is clearly possible and probably also fairly trivial (considering the existing work on bezier curves et al.)
The text was updated successfully, but these errors were encountered: