Search the Community

So I am trying to create a letter with a line laced through it. So I create the letter (let's say A), then I create a path using the pen tool. And then do a divide operation so that I can bring the path or letter to the front with each cut out part. But it divides fine for every cut except for the second cut, where it only creates one part where it is supposed to create 2. Steps to reproduce: 1. Create a letter (I used A) using the artistic tool 2. Draw a continuous line using the pen tool, zig zag across the letter 3. Select the line, and then do layer->expand stroke 4. Duplicate the letter 5. Select the duplicated letter layer and the line, click Divide from the boolean operations list I have attached an image of the issue, most of the divisions are correct, except for the selected division which should ideally have one more cut, but dint seem to cut it correct.

Hi, I'm currently using the trial version of Affinity Designer and just testing the software. When I use the divide boolean operation, it makes my object move, I've added some screenshots for more clarification. See the guides for reference of the position. BEFORE: AFTER:

I’ve noticed quite a few multiple feature request 'wish list' posting recently on the Affinity forums. I've an idea the posts might be born out of three areas of frustration (beyond people not reading the forum rules): Difficulty searching the forum to find the most relevant post. For example, 'knife tool' finds numerous posts, (12 forum pages worth!). Features/tools can be described in different ways. For example, 'cut tool', 'knife tool', 'scissors tool' etc. Essential/basic features have been missing or broken now for a long time. For example, true vector brushes, warp tool and faulty Boolean Divide operation.* I really thought Serif/Affinity were on the right track when they started off publishing a roadmap showing their future plans. At least it shared their thinking and priorities helping to manage users expectations. Of course with three main products and Windows, Mac and iPad variants, life is more complicated now. I'm not quite sure what the answer to all this is, ie to ensure Serif benefit and gain useful insight from any feedback and we (forum members) feel our voices have not fallen on deaf ears. I do feel this needs to be addressed as it's only going to get worse. There are already over 15,000 posts in the current Affinity Designer Feedback forum and even more (31,000) in the older feedback forum. At the end of the day I believe Affinity forum users need a quick and simple way to check that 'their' missing/broken tool or feature request has already been requested/reported and importantly has been properly considered and acknowledged by Serif staff. Thanks *(I recently managed to get over 900,000 objects dividing just 42 shapes. Although small credit to Affinity Designer, despite wasting a lot of time, it didn't crash, although it did take an equally long time to undo!) 😐

As many of you I recently moved from Illustrator / Photoshop to Affinity's alternatives because of the pricing issue. Design has become more of a hobby, and I can't justify a monthly subscription. Overall, I am really impressed with the applications (Designer / Photo, mac and iPad), but one thing I really painfully miss from Illustrator, though, is I heavily relied on the Pathfinder, more specifically the "Divide" operation. I was used to, for example, divide shapes using a curve, or divide multiple shapes to very reliably. As many pointed out, the experience in Designer is less than perfect - for one, you can only combine shapes with other shapes, and even so, in simple divisions, you get a ton of unwanted curves spliced off the intersections. I saw a bunch of posts describing the problem, but not really a lot of workarounds or solutions. So I'm writing this post to see if I can get something a little more constructive than 'Divide is still garbage' comments. So I guess I have 2 questions. One for the dev team: Where does this fall on your roadmap? Can you shed a light on if and when can we expect to see reliable divides integrated on the app? Another for the community: Do you have some good techniques / workarounds that you've found to overcome the divide limitations that you could share? Thanks in advance!