matt.baker

@Chris BIs there any more news on this, please? Even the boolean workarounds don't work for me. Add and intersect just keep the original rotated bounding box. This means the create artboard from selection is far too big as it's using the bounding box diagonals. Maybe it could be an option called flatten transforms.

The DPI field on the export dialog is limited to 1024, but the document DPI can be much higher than this (32-bit signed integer) - for example, 2540. If you set the export to use the document DPI it works as expected. I appreciate DPIs above 1000 are unlikely to be used in normal situations, but if the document supports it, so too should the export (if technically possible depending on the output format). Unfortunately I have to use such a high DPI in certain circumstances because Affinity doesn't respect the document units during export to SVG and always goes back to pixels... By setting the DPI to a multiple of 254, I can get the accuracy I require in the final export dimensions. As a side note, I've noticed that increasing the document DPI above ~32'000 messes up the document dimensions. A corner-case, but could be better handled.

I just remembered that this is probably due to the tiny size of the document; Still a bug though It was part of an export from a PCB design Would be nice if this was implemented:

Before: After: Document: Expand stroke bug.afdesign

Ooooh, it looks like setting the Page Box actually changes the embedded document canvas to match the content size, not just on the Container document. I.e. this does what I wanted from the start. Designer_tQnu8qwUzl.mp4

@walt.farrell Sorry for the delayed reply. In your last step, is the embedded document's bounding box not still the same dimensions? For me it is. I was expecting the bounding box to shrink to match the contents like it does for non embedded documents. Setting the Page Box to Minimum or Maximum Content results in this after performing the previous steps, which looks like it could be another bug: However, it seems to work if the embedded document is left unchanged:

@walt.farrell I'm using an Affinity Designer file for the embedded file (example attached) Container.afdesign To embed.afdesign @Old Bruce Yep, I'm using the Selection choice. Perhaps it's Windows specific. Also occurs in the latest 1.10 Beta. Embedded edit behaviour screen capture: Embedded behaviour.mp4 Non embedded / expected behaviour screen capture: Normal behaviour.mp4

I would like a button somewhere that allows you to set the document/canvas size to fit the contents. A workaround is to select everything, insert an Artboard based on the selection and then delete the Artboard while keeping the contents. However, this trick doesn't work in embedded documents.

That is what I'm expecting in this case, yes. I wouldn't normally draw something like this, but it's from another design that I am trying to optimise by converting to expanded stokes. On this element they had 3 circles 2 with strokes all overlayed which could have been simplified to a single torus (black and white symbol). A bit of a mess.

Thanks. Should this not be more intuitive though, so that Affinity does the work automatically? I see that it works when an another inner torus is included

If I have two 2d projected torus shapes overlayed with the same centre point and perform a boolean add the centre is filled in. I would have expected this to have remained hollow. These do not have a stroke width and are curves with hollows. I know that this can we worked around by adding, dividing and then subtracting. 9CyVyp2Bi2.mp4 Add bug.afdesign

The mitre rendering for the elements in the attached are inconsistent when zooming in/out even when making the document 1000 mm tall (it worked for the expand stroke bug). Precise clipping is enabled in preferences. pyJayumayV.mp4 WEEE.afdesign

You're right. I forgot it was such a small element. I was hoping that Affinity was doing some sort of relative scaling based on the overall document size so this wouldn't have much effect, but looks like it doesn't. Increasing the size and then performing the expand stroke does fix it. Thanks It was taken from the attached where the symbol is typically <10 mm tall when reproduced on physical media. WEEE.afdesign

Expand stroke bug seems to be a long standing issue. I've tested this in the main release and the beta with the same result (source attached). Any ideas why it's doing this? It appears to be a closed path. cTeHmHHrEw.mp4 Expand stroke bug.afdesign

@Chris B forcing an update of the display drivers on my Surface Pro 5 from the Microsoft 09/2020 Surface specific (latest available) to Intel 02/2021 ones has fixed the problem. My comment still stands about the UX though with a progress bar / operation cancellation.