I’ve been using Lunacy for months now after abandoning and avoiding Figma to force adoption of a local first alternative. My experience during this month has been Great for the most part, the app runs smoothly and the ui gets out of my way when I need more space, but one thing I just can’t get over is how useless the Flatten tool is compared to Figma. Why does it work differently and are there any plans to change or improve this?
Could you please tell us what isn’t working the way you expect? Any examples or specific scenarios would be greatly appreciated.
In figma the flatten option works on paths without removing intersecting lines and isn’t just a flattened union. This allows for single layer custom line icons and multi colour shapes which my workflow relys on to replicate application icons. Additionally I can’t even connect multiple lines to a single vertex because its either a shape or a line. I could share examples if needed
If possible, please share a short screen recording or a few screenshots of the issue so we have a better understanding of the situation.
I Tried to keep it compressed, hopefully you can see the issue. You can check either video, the shorter one is just at 2x speed for your convenience.
Hello?
Thanks for sharing the screencast! We’ll need some time to look into this issue. I’ll get back to you as soon as I have any news.
Thanks, as long as it’s being looked into. Also the link expires in 1 day and 13hrs
We’ve looked into it, and unfortunately, unlike Figma, Lunacy doesn’t support vector networks. That means a single shape can’t be made up of multiple separate lines or paths, so there’s no way to achieve the result you’re looking for at the moment.
I figured it’s not supported and it’s part of the reason why my .fig files for ux still breaks despite the v15 improvements. According to what I learnt from figma, It’s a difference in how they handle vectors, Graph-Based Vector Networks versus Contour-Based Bezier Paths, or so it says.
Additionally, would it be possible to mimic this behavior at the UX level by anchoring co-located nodes across different paths when flattening?
This could function as a compound layer type appearing as a single object in the UI, while remaining multiple paths and shapes under the hood. This system might also aid in the translation/import of .fig files, though it may be more complicated than I presume.
First of all, thanks for your suggestion!
We have looked into it, and while this is technically possible, it is quite a complex task. So we are unlikely to be able to take it on at the moment, unfortunately.
That’s okay, never expected it to be a quick fix, you’re probably already working on something big, as long as it’s considered and possibly attempted in the future then That’s enough for me.