Skip to content

[Feature request] Dash path effect improvement #503

Description

@samytichadou

Dash path effect only have size parameter for now.
A big improvement would be to have a spacing parameter, and an offset one.

  • Size : (float -inf to inf) length of a dash
  • Spacing : (float -inf to inf) Length between two dashes
  • Offset : (float -inf to inf) Move all the content (dashes) on the path
  • number of dash elements : (integer 0 to inf) to be able animate their apparition

This would allow to have a single dash moving along a path with this effect, and to customize more the dashes aspect !

What do you think ?

Activity

  1. pgilfernandez commented on Apr 10, 2025

    @pgilfernandez

    Yes, you are right, that would be a nice improvement.
    I will have a look at it next week 💪🏻

  2. samytichadou commented on Apr 10, 2025

    @samytichadou
    Author

    Yes, you are right, that would be a nice improvement. I will have a look at it next week 💪🏻

    thanks you ! do not hesitate if you have question about it !

    An extra parameter could also be number of dash elements (integer) to animate their apparition ?

  3. added this to the 1.1.0 milestone on Apr 10, 2025
  4. added theissue type on Apr 10, 2025
  5. pgilfernandez commented on Apr 12, 2025

    @pgilfernandez

    Done! #505

    Image

    I did not implemented number of elements as, even if I did some tests ,it did not work properly as it is difficult to control them because it depends on the path length and size in the canvas. Anyway, it could be controlled with the sup-path effect and animate the complete parameter

  6. samytichadou commented on Apr 12, 2025

    @samytichadou
    Author

    Perfect ! nice addition, thanks a lot !

    If i may, scale seems confusing to me, it implies scaling something which have a defined length/size. Size would be a better way of describing it. What was your point in changing it ? (genuine question i do not understand :) )

    Edit : ok i got it, sorry for the misunderstanding !
    So the scale parameter scales the entire dashes including spacing between them ? that is perfect ! what is the anchor point of this scaling ? origin node of the path ?

    And of course no problem with number of elements,

    it could be controlled with the sup-path effect

    It could, but you'll have to put a lot of precise keyframes if you want to avoid a dash being cut in half, having a number of element integer value would greatly improve animatability :)

    If you prefer, i'll make another issue about only this parameter ?

  7. pgilfernandez commented on Apr 12, 2025

    @pgilfernandez

    Edit : ok i got it, sorry for the misunderstanding ! So the scale parameter scales the entire dashes including spacing between them ? that is perfect ! what is the anchor point of this scaling ? origin node of the path ?

    Yes, it "scales" everything. It was called size but I would say scale fits better but @rodlie has the last word. And yes, it's node 0 (remember you can check it with Point mode tool and pressing shift + ctrl or shift + cmd.

    And of course no problem with number of elements,

    it could be controlled with the sup-path effect

    It could, but you'll have to put a lot of precise keyframes if you want to avoid a dash being cut in half, having a number of element integer value would greatly improve animatability :)

    By the time being is the only way...

    If you prefer, i'll make another issue about only this parameter ?

    Maybe yes, that way we can close this one when the feature is merged (once again, if @rodlie finds it mergeable as it will break old files and blablabla.... BTW, I guess that, if merged, it will be done for v1.1). You may try it out with GitHub Actions.

  8. samytichadou commented on Apr 14, 2025

    @samytichadou
    Author

    Yes, it "scales" everything. It was called size but I would say scale fits better but @rodlie has the last word. And yes, it's node 0 (remember you can check it with Point mode tool and pressing shift + ctrl or shift + cmd.

    perfect ! and thanks for the tip i did not know about that ! :)

    Maybe yes, that way we can close this one when the feature is merged (once again, if @rodlie finds it mergeable as it will break old files and blablabla....

    all right i'll do that once it merged ! thanks for your pr that is awesome !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions