# Paths scaling issue

**URL:** <https://doubleandthrice.discourse.group/t/paths-scaling-issue/12>\
**Category:** McKinley\
**Created:** [July 12, 2026, 9:27am UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12 "2026-07-12T09:27:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![acvivo](https://yyz2.discourse-cdn.com/flex052/user_avatar/doubleandthrice.discourse.group/acvivo/32/9_2.png) [@acvivo](https://doubleandthrice.discourse.group/u/acvivo)\
**Post date:** [July 12, 2026, 9:27am UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12/1 "2026-07-12T09:27:26Z")

</div>

Hello there,

I’m testing McKinley and I love it. I was waiting for an SFSymbol creator like this one for ages.

I just found a weird issue. I wanted to create a semicircle path so I cerated a circle, converted it to paths and removed some portions. I did it several times to create more copies and scaled them to position them. I set all the paths width to 1, and are presented as such in the editor, but when I export to symbol and open the svg in Figma I see that the paths have different widths, as if the scaling was taken into account when exporting. I also see the onion on a different place as the selected path. Let me know if you need the .mck file, I don’t know how to add it to this topic.

Thanks for making this app.

---

<div class="post-metadata">

**Author:** ![AmyWorrall](https://yyz2.discourse-cdn.com/flex052/user_avatar/doubleandthrice.discourse.group/amyworrall/32/5_2.png) [@AmyWorrall](https://doubleandthrice.discourse.group/u/AmyWorrall)\
**Post date:** [July 12, 2026, 2:07pm UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12/2 "2026-07-12T14:07:58Z")

</div>

Thanks for the report and the file, I’m looking into it now.

---

<div class="post-metadata">

**Author:** ![AmyWorrall](https://yyz2.discourse-cdn.com/flex052/user_avatar/doubleandthrice.discourse.group/amyworrall/32/5_2.png) [@AmyWorrall](https://doubleandthrice.discourse.group/u/AmyWorrall)\
**Post date:** [July 12, 2026, 3:57pm UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12/3 "2026-07-12T15:57:13Z")

</div>

![image](https://canada1.discourse-cdn.com/flex052/uploads/doubleandthrice/original/1X/8f67abbe3c86402a223d84b2583c17f01b45c415.png)

Got it!

The issue was the ordering in which different transforms were applied, compared to the convert-strokes-to-outlines step, was different in the canvas renderer and the export compiler. It only showed up when there were a few transforms applied at once (eg a path itself was transformed and was also in a group that was transformed).

Fix is now coded (this is a screenshot of the exported representation in Illustrator). I’ll push a new build of McKinley later today.

---

<div class="post-metadata">

**Author:** ![AmyWorrall](https://yyz2.discourse-cdn.com/flex052/user_avatar/doubleandthrice.discourse.group/amyworrall/32/5_2.png) [@AmyWorrall](https://doubleandthrice.discourse.group/u/AmyWorrall)\
**Post date:** [July 12, 2026, 5:13pm UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12/4 "2026-07-12T17:13:47Z")

</div>

New build, with the fix, is now on TestFlight.

---

<div class="post-metadata">

**Author:** ![AmyWorrall](https://yyz2.discourse-cdn.com/flex052/user_avatar/doubleandthrice.discourse.group/amyworrall/32/5_2.png) [@AmyWorrall](https://doubleandthrice.discourse.group/u/AmyWorrall)\
**Post date:** [September 22, 2026, 10:55pm UTC](https://doubleandthrice.discourse.group/t/paths-scaling-issue/12/5 "2026-09-22T22:55:42Z")

</div>