ELinder

Obviously it can also be a global setting for new documents or new elements in a documents, as it already is that. It's set to OFF. When manually toggled it would carry over as it does now with the object, but any new elements should default to ON if we want it. Same with the corner tool, it currently does not carry over when scaling an object. It really should.

Is there a way to globally enable stroke "scale with object" and corner tool settings scaling with object to always be enabled unless turned off? I've never had an occasion where I didn't want both to happen, and it's a pain to redo both when I happen to reuse some previous object. Especially the corner tool settings, I find it almost impossible to exactly recreate the original corner radius setting after I've resized something.

Matt, I'm glad to hear that it's been fixed internally. However, when the list of fixes for the beta versions always include lines like "miscellaneous bug fixes and crash fixes" how are we to know what is or is not covered by that? I've said it before and I'll say it again, if you're going to have beta versions, it needs to be done more systematically. Do you want people to just use the betas and generally see what happens, or do you want them to hammer specific problem areas? The list of specific things that are being worked for each release needs to include the bug numbers. Failing that at least give the registered beta testers the ability to read a bug tracking log to see what's fixed, what's actively being worked on, or still in the queue to be looked at. Erich

Divide is still broken in this release candidate.

No response here either? I fear the fix for this is such a major boolean re-write that they're pushing off a fix until they go to version 2 of the program. Erich

This bug has been previously reported by many people and for a long time. Is it finally going to be addressed in this 1.9 cycle?

Thanks for the confirmation. I've tried multiple ways, and duplicate paths are the most flexible. Erich

Is it not possible to have multiple text sections on the same part of a path? Whenever I start a new text section it automatically goes to the other side of my path. For example, I'm trying to move "England" next to "New Zealand", but when I drag it around it is upside down on the wrong side of the path. If I highlight select it and use the Reverse Text Path tool it reverses everything on that path, not just the highlighted text section. The only way I've been able to figure out how to do this is multiple duplicates of the same path and have each word on a different identical path, or to add a lot of spaces to the text and make it all one huge line on the same path. Erich

Almost a year and 5 updates later, and the divide function bug is still present in Designer Mac 1.8.4. That's just plain ridiculous for a core program function. Erich

I quite like that! I was struggling a bit with keeping the definition of the teeth in the middle from spreading out too much. Erich

Thanks all

Yeah, that could work, and it's better than using an inner glow with the background color since the final background won't be a solid color as it is in this example. I'd still like to know if there's a way to put a gradient transparency across each tooth. Erich

I'm trying to figure out a way to apply a transparency to the edges of cog teeth so they blend together with the background along the long edge of the teeth for each individual tooth. Is there a way to do this? So for the image, I want the brighter teeth to blend into the background so the long edges of each tooth is feathered. cog-tooth-fade-edges.afdesign

Thank you again, that did the trick! I can now export directly from Designer to SVG and into Lightwave3D without going thru any other programs. Erich

Thanks for looking at the files. Using the Flatten Transforms solves the positional errors (although I thought I had tried that before), but the colors are still not brought over. Everything is 0,0,0 black. That's what's so bizarre, the exact same SVG imported to Pixelmator Pro (or any number of programs) does carry over the colors. The SVG I re-export from Pixelmator Pro when imported to Lightwave3D does carry over the colors, but the SVG from Designer does not. Designer is doing something different with respect to how it writes the colors for each area into the SVG. Erich

I've found something odd when using an SVG file exported from Designer 1.8.3 Mac. I created something simple in Designer, converted everything to curves, used Separate Curves to expand the hole cutout polygons, and exported as an SVG. When I import that into my 3D program Lightwave3D, I get strange results. If I take that same SVG file, import it into Pixelmator Pro, and re-export it as an SVG without changing anything, it properly imports into Lightwave3D. I've tried various combinations of the SVG export options in the More dialog, but still no dice. Is this a Designer export bug, or simply some other version of SVG file format? SVG-file-versions.zip

The newest Affinity Designer Customer Beta (1.8.3.0 - Release Candidate) fixes lists: - Improved boolean geometry results. Given the multiple different boolean operations that have problem, how about being more specific? Why not actually list the bug numbers so we can know if our problems have been at least looked at? thanks

In 3D apps any kind of boolean operation is messy. That's why there is also some kind of stand alone "merge points" function to merge co-located points. There's also a setting to change how close the points are that you can adjust before doing the operation. I wonder if something like that would be useful for these kinds of problems.

Well darn, my hopes were that the improvements in Booleans included bug 'afd-2042'. Speaking of which, it would be very helpful to include specific bug numbers where appropriate in the list of fixes and improvements for the beta releases. Erich

OK, thanks for the update. BTW, the workbook really is an excellent way to learn the program. Erich

Thanks for the info. Is there any indication when the divide issues will be looked at? It's particularly irksome when an official Affinity Workbook tutorial can't be followed because of this bug. Boolean problems seem to be a fairly long-existing problem on what should be a core function. I'm fairly new to the program, but I can't imagine what others are doing without clean booleans. Is there an older version we can use that works properly? I don't have Photo or Publisher, so exchange compatibility isn't an issue for me. Erich

Does the bug fix list for Beta 1.7.3 (RC1) list all fixes? I just tried the divide problem detailed in this thread, and it is still there. Erich

I took the above example scene and operated on only the inner wedge of curves. When adding you can see that not only are co-positional points not properly welded together, but extra points are added where they should not be. The further example has the history also saved to it. Erich error_example-further.afdesign

OK, thanks! Erich

I looked at this example to see if it's related to one I recently posted. I do 3D modeling also, and it looks like issues I've had in that realm where points that are supposedly co-positional are not properly welded together in the boolean operations even when they should be. The results in slightly different curve shapes left over, so the boolean operations do not work as they should. Erich