Jump to content
You must now use your email address to sign in [click for more info] ×

Mikeware

Members
  • Posts

    5
  • Joined

  • Last visited

  1. It'd be great in the export dialog to have a Rotate 90, 180, 270 degree option (across products). Sometimes printers need files in a landscape/portrait/orientation, but that may not align to how the document/image actually reads. Therefore, rather than having to keep the doc and resulting image in-sync for orientation, it'd be great to just be able to select that as an option during the export/rasterization process quickly and easily. It'd be especially helpful if needing to export to more loseless formats as then another step isn't required before (and disrupt workflow) or after (and disrupt quality of resaving). Thanks!
  2. This very much confused me as well. I went to export my images, and expect the 'Nearest Neighbour' to apply this on export to everything so I have no anti-aliasing in the final output. It's unintuitive to have to apply this to a per-layer basis within my document. This is something I want to change how the vector lines map on export for the document I'm creating at that time and select my different filtering options. Nearest Neighbour should provide me with the option for no aliasing, that's how it's documented in the help: I expect this setting in the export dialogue to make a visible change, from what I can see, any of the settings effectively do the same thing and are indistinguishable... so what's the point then? See this with both PNG and WEBP formats. This wasted I don't know how much of my time, and required me to find this post with the link to the blend options, no way I would have associated that or discovered that otherwise. It's part of the export process, there's a setting there, it's what's intuitive and expected of the setting, and is documented for that purpose. It should perform that operation.
  3. Thanks @Sean P, and updates from dev, were they able to reproduce the issue? Just curious what the update cycle looks like and when a fix may be available?
  4. @Komatös the background is inconsequential to the problem, it's just from the screen clip I took in the designer vs. Edge which displays a white background by default. The resulting SVG is properly transparent when loaded in other tools. The problem is the dash array is not exported correctly, so the SVG image (the one with the solid white background) the openings in the circle stroke are facing away from each other compared to the original design created where the openings are facing each other more. This gets exaggerated more depending on the geometry of the transforms on the shape and the dash array used, but whatever is writing the SVG and reading it back in for stroke-dasharray is doing the math wrong in both directions as the problem round-trips.
  5. Using version 1.9.2.1035 from the Microsoft Store on Windows. I used the stroke dashes on a circle in the designer and exported as an SVG. In the designer for the attached afdesign file and when loading the exported SVG I see this: However, if you load the SVG in any other tool (like Firefox, Edge, or a UWP app), the stroke-dasharray value is displayed like this: Since Affinity Designer round-trips properly, it seems like the write and read from stroke-dasharray is done incorrectly between whatever representation AF Designer uses compared to the SVG spec. This is making the design I created in AF Designer unusable as an SVG in my final product, as it's not represented the same. So to recap: 1. Create a new AF Design document in .afdesign format. 2. Modify the stroke dashes on an element like a Circle. 3. Export that to SVG (for export) 4. Load SVG outside of AF Designer (in a browser for instance) Note: exported SVG doesn't match the design created in the designer. stroke-dasharray value is incorrect in exported SVG style. I would expect from the designed afdesign file to see the same pattern when loaded in an external tool. After changes to AF Designer, I wouldn't expect the afdesign file/format to change (otherwise my existing design would be effected). I would expect when I re-export to SVG again that the resulting SVG would now have the proper stroke-dasharray to match my original design. Thanks! bad.afdesign bad.svg
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.