Export issues
-
But exporting as PDF places the objects somewhere off the page. This needs investigating by the developer. (It's great that you posted the file, btw).
The same thing happens with the SVG.
The decimal trick mitigated the main issue, thanks!
-
@Ingolf I'm not suggesting you to change its size, just to increase Precision on Export from 2 to 3.
-
I'm not suggesting you to change its size, just to increase Precision on Export from 2 to 3.
Yep, got it. But why is the default 2 then?
-
I guess it's in order to generate smaller files.
-
@b77 What can I do to add decimals for more precision when copy-pasting small areas to other programs from VS? I still see the issue when copy-pasting.
-
@Ingolf I don't see the problem here so I'm not sure, but you can increase decimal values in Preferences > Number Editors.
-
Increased them all to 6, no dice.
@vectoradmin This is what happens and as you can see the issue with recurring borders I removed several times occur again. The copy-pasted image looks nothing like the original in VS, and exporting the file results in the borders as well.
🍏 macOS Sequoia Apple Silicon
-
@Ingolf Let me try again. It looks like something's wrong with the thick contour shape. I would break it apart (Object menu), move the smaller part above the bigger part and subtract it from it. Maybe it helps.
-
Thank you for your time and you think creative, I'll give you that. I forgot to move the smaller part up, but even when I did, the results are the same. When the resulting piece moved away from the main shape, I gave up.
The break apart keyboard shortcut was also a slow starter. I am not sure this program is ready for a commercial launch.
-
@Ingolf It is not clear what is going on here. What is the size of that bird (dimensions)?
The decimals in preferences refer to what is shown in the number editors in the UI, it does not affect export (copy to clipboard) precision.
If possible, you can send me the file to csraba at vectorstyler.com and I will try to replicate. -
@Ingolf This issue should be fixed in the new build 1.1.002 (beta)
