Incorrect work of the Motion extension
![example.svg](/uploads/bae8fdf322755614618054a215676f41/example.svg)<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> Incorrect work of the Motion extension on all shapes generated by incscape (see attached file). #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - draw any shape (polygon, star, ellipse) - convert shape to path - open Extensions -- Generate from Path -- Motion - for ellipse: - set length to 50 - set angle to 90 - for others: - set length to 10 - set angle to 30 - press live preview or apply #### What happened? incorrect figure of extrusion is displayed (see attachment). #### What should have happened? correct figure of extrusion Sample attachments: <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> #### Version info version 1.3 ![example.svg](/uploads/76a7fa3c78a728c38e64a1651833a073/example.svg) <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->
issue