WhiteX

As far as I know, the background color always "shines through" on similar cases. Ie. having perfectly aligned shapes, with the end nodes aligned to the same exact location (with snapping), you still see a white line (or dark, depending on your background) at the area of contact. It's a pretty ugly thing and always needs workarounds. Would be nice if @serif would fix it.

+1 I miss that feature... Doing it all the time manually is timeconsuming...

Yes, I know about that @reglico, but we're trying to replicate some kind of "shape builder" functionality, and if we divide multiple shapes with a stroke that has been converted to curves, we won't be able to merge them with boolean operations afterwards, because the width of the stroke will make a gap between the parts... So, as a first step it would be nice to be able to "divide" shapes using strokes. Edit: Most of the functionality is already present, we would need some advanced selection features (see second part of the inkscape video): Once that selection feature is implemented it would be "nice to have" that the selected shapes would be somehow highlighted, but if we'll get the advanced selection feature, that'll be almost enough

+1 We need this.

+1 This would save a lot of time when creating complex shapes! I can live with the existing tools too, but when we need to divide a shape into multiple different shapes, using something similar as mentioned above, would be really helpful. Alternately, using lines as dividers would also help. Right now you can make boolean operations only using shapes, not with shapes + lines (or curves without closed ends). This would be a big steps towards the perfect shape building tool.

@mredig It's been three years... Please, we need a solution already.

Three years passed and there's no significant improvement regarding this matter. Just saying. Please do something with this.

Any news Serif?

That's the exact same problem I had / have, just with the A4 print size. Either of the provided print templates convert to whole pixel units unfortunately. What I do in such a case is, I create an artboard with a print template (A4, Letter, etc), then I change the document units to pixels, change any values to whole numbers (coordinates and sizes), and that's it. The document will have virtually the same physical size. Any printshop should accept them.... but this is still a workaround. In your case you can create the artboard in the desired size in inch or other units, and before exporting, just switch to pixel units and correct the numbers. I'm not sure why can't be this done automatically during the export, but it would be great if we could just take care of the design work. In an ideal world we would not have to deal with pixel peeping / tweaking in a VECTOR app...

@RGerhart I complained about this too. There's no fix, there are only workarounds... You need to have your artboards positioned at whole pixel coordinates and they need to have whole pixel sizes. This "fixes" the issue. Serif, we still need a real fix to this. Thanks.

Come on, it's been two years since we wait for this feature It's really important! Any news?

Sorry for resurrecting this topic, but now it's more relevant than ever. I think this is a great idea, so anyone who is an Extensis customer or is thinking about purchasing Suitcase Fusion, please contact them: https://www.extensis.com/contact/ and let them know that we really need font auto activation for Affinity Designer / Photo / Publisher (and the rest that comes). Using Application Sets is not a viable option. I just did that. Let's create some momentum.

If this can't be corrected from the software, maybe it would be beneficial to have a warning message from AD/AP during exporting that duplicate fonts were found in the document and it can cause inaccurate results.

This problem occurs to me too every once in a while with different fonts. Maybe a solution from Serif would be the best. Deleting the font cache did not help for me either.

Any news regarding this problem? It's killing me... And yes, @4dimage it's related to font caching, I found some help in other topics, but this does not solve the problem fully on Windows. The idea is to clear the windows font cache. There are some changes, but some characters are not working. On Mac works well though. We need a solution for windows users.