MmmMaarten

Well, it depends on what you mean by attracting. There is snapping (the magnet button):

@G13RL Yes, I know that way it works by leaving the paths in place and only moving a single node to join. Never had problems with that. But most of, if not all, the time I'd like to move the full curve to the right position, where nodes are on top of the nodes of the other curve, and then join the paths. I tried it again here by trying to select 2 nodes that are on top of each other after placing one curve exactly on top of the other, but it doesn't work. It looks like it's impossible to select two nodes that are on top of each other to me. It's like it only selects the node that's on top. How to do you do this? Test 1: See below (can't move the video on this forum as it seems 😓) Test 2 (reversed) --> If I join the other ends of the curve first the join works, but the close path still adds a redundant node. join-and-close-reversed.m4v Test 1: join-and-close-2.m4v

The following shows an extra added node on join and close. Eventhough the nodes are exactly on the target nodes. The extra node is created under the node that turned yellow when putting it on top of the other node, so that should be exact. So what should I do differently to prevent the extra node? (I provided the file in the attachment) join-and-close.m4v test.afdesign

Yes as @G13RL I was about to post pretty much the same video. The only thing I would do differently is first putting the nodes of the curve on top on the exact same place as where they should be by dragging them to the spot they snap to the other curve and after that hit 'join curve'. There's one thing I don't know as I'm no expert on join curves and that is that the last join and close will add an extra node, which is obviously not what we're after. Do you happen to know how to prevent that @G13RL ?

Ah I see. Than indeed the instructions you found on join path should work. It's a little difficult to tell what's going on with that video alone. Maybe you're using join in a different way or there are nodes on top of each other perhaps? It would be easier to help you if you could provide the afdesign file

The instruction post uses a single OPEN line path to connect to a single OPEN line path. But you try to do something different: you are trying to connect a closed path with another closed path. You cannot do that with join. You cannot connect a node to a crossing path, only to an end point. If you combine two paths, you first fill the path, select both paths, and than you can use a boolean Add-operation to add one path to the other making them one path. Is this what you're after? Boolean-Add-1.m4v

You posted your issue in the wrong forum. Serif might find your post if you post it in the right forum. For Mac it's here: https://forum.affinity.serif.com/index.php?/forum/77-photo-bugs-found-on-macos/

It was not that 'Easily reproduced' for me, as I use four of my own svg export presets depending of the needed output and I never had this issue before and tested it on all four of those exports. So my presets work fine, but the build in SVG for export preset doesn't. So I just compared the settings in my presets with the preset having the issue (SVG Export, but probably the other build in presets as well?) and found the difference: In all my SVG export presets I have 'flatten transforms' enabled preventing the created groups. But with the default SVG Export preset this isn not checked. Without 'flatten transforms' enabled Designer wraps the <path>s in extra groups just to apply transforms. But instead it should apply the transforms to the <path>s and not create extra groups as this disturbs the hierarchy inside the svg. I agree creating extra groups by the exporter is wrong and should never happen. There are other posts on this forum about redundant groups in svg too.

I am too. Look again at the example, it's just one object.

@haakoo Also this method can only be used with filled shapes and not with groups or sublayers. Also try using the shape on the left (just a stroke) and use boolean Add. This changes the shape:

Yeah, you can tell. Although the grand scheme of things is nice for overview, real magic happens in the details. Perfectionism could get in our way and there's a limit, but it's also underrated as life is all about details

I reacted to Walt's Layer --> Geometry --> Add. Thought that was a long way for just pressing the boolean Add. I understand now you already mentioned that before. Great workaround @haakoo! About nodes not changing: I'm not sure about that. When we combine different shapes with a boolean add a lot of times the nodes change or new nodes are added / nodes are removed. Also when not really needed. What I mean by changing nodes is that I'm not sure if boolean adding itself to itself don't cause the shape to change or nodes to have rounding-errors after this boolean operation. If these are really boolean operations in code they shouldn't, but I am not so sure about that and just to reset a bounding box that could be a risky workaround. Also that conversion indeed. We make a change in the layout here, just to reset the boundingbox. That's not what I would like to see when just resetting the boudingbox.

That's a great workaround indeed! BTW, you can also directly hit the Boolean 'ADD' button with the object selected. If it is so simple to reset the boundingbox like this... than perhaps Affinity could make a shortcut for this that's called 'Reset boundingbox'? [Edit] Oh no, that would probably not be such a great idea, as using the boolean / geometry tools probably change the shape/nodes/

If the animation is meant for video you could take a look at Davinci Resolve and learn Fusion. It has a free version with practically all features. Davinci and the Fusion page have a learning curve which takes you a while in Fusion, but once you know your way around you can do pretty much anything with it animation/VFX wise. Like importing a svg with your signature you created with Designer and make it animate. But easier and faster to learn would be other (paid) animation software like Adobe Animate CC or alike.

I've experienced the same issue yesterday too on a Surface Book 2 (Affinity Designer 1.8.3); pen 'suddenly' didn't move the object and needed to reload the project in order to make it work again.

I just downloaded your afdesign-file to open it in Designer and exported it to svg. But the generated svg doesn't contain any <g> groups. I tried both with raster output enabled as well as with raster output disabled in the exporter, but both have the same result: no groups. Also when importing the created SVG in Designer Designer doesn't show any groups. So not sure what issue you are facing, but I can't reproduce it here with the given file (Designer 1.8.3)

I have the same dragging-issue with Designer 1.8.3 on a Surface Book 2. It's a pain/impossible to design and draw when it's so sensitive to movements and moves your stuff around all the time while practically holding the pen still. It's pretty frustrating. I had to lock all my layers just to be sure they were not being moved, so I agree this makes the pen-on-tablet workflow pretty much useless. After turning Windows Ink off pressure sensitivity doesn't work anymore, so unfortunately that's not an option either. I had to grab my mouse all the time to prevent these issues and after a while switched to a different computer with a seperate wacom tablet (intuos 4) as it was impossible to draw in Designer on a Surface with the pen (also because of other issues with the pen in Designer) 😪 A fix would be highly appreciated!

@T V I'm out of likes and thanks to spend on this forum, so like this: great hints, thanks! 😀

Hi, Using a Wacom tablet or mouse I am able to add nodes to an existing path by clicking on the path (using the node tool). But when using a Surface Book 2 pen clicking on the path doesn't add nodes. It only shows the position where the new node might be added. I searched through the Designer settings and found 'Enable Pointer Support' in the UI section. But checking that setting and restarting Designer didn't fix this. When I turn off Windows Ink in the Designer Tool-settings and restart Designer it fixes this issue, but than there is another issue as the pressure sensitivity of the pen isn't working anymore. So that's not a solution unfortunately. Using the Surface pen to draw without the full node tool functionality is a pain. I might be missing something, but this looks like an issue in Designer. Love working with Designer and love the Surface Book 2, but it would be great to use Designer on the Surface book with its pen as that's an important reason buying this Surface Book! 😀 designer-pen-issue-node-tool.mp4

Moved this to:

Not sure what you mean by 'weird behaviour', but for your information; the url in your original post points to a different location then the one in your last post. The initial url points to https://boroji.com/test/index.html , but the url in your last post points to https://boroji.com/ (so without the 'test/'). In the last url we can even add index.html or index.php and it still redirects to the right page. If you remove the 'test/' from the url in your initial post it works just fine.

Love this style! 😊 Great work!

Amazing work! Also the other butterflies and also animals on your Behance page. Incredible. Such details and colors and textures while never to shouting. Love it! BTW Also like your clean UI design for the Redominator. There are a lot of crowded or shouting plugin interfaces around, but this one just breaths quality and envites to play with it.

There are some issues with using automated fields in text: - After loading a file, page number fields in the open page show as a hashtag (#) instead of the actual value. Only after refreshing the page by clicking around it gets its actual value. - In the master pages for some reason the Total Pages field is shown as a value (the actual page count), but the Page Number field is showing a hashtag symbol (#) instead of its value. To me that seems inconsistent and gives me the impression as a user this part of the software is not stable yet. I would expect both fields to show their values or both fields to show some symbol representing them, but not both using a different method. See video below and file in attachment. Field-Issues-1.m4v test.afpub

After inserting fields it seems impossible to see in the viewer what fields are inserted. We can use 'Highlight fields', but it only shows THAT there are fields in use and where they are. They don't show WHAT fields. Also there doesn't seem to be a way to change or remove automatic fields from a text instead of removing the text and inserting another field. There are <fieldname> texts in layer names, but: - This is not a visual representation of the fields in the actual view, which is what I'm after and is important to locate/debug fields without guessing Next to that: - We want to give layers names, so than this isn't visible anymore AFAIK - Fields can also be used inside other (larger) texts, so that makes it impossible to show and locate these fields - We use a visual editor to edit visually, not guessing from a layers name where the field might be in the visual viewer Also: - There seem to be an issue in the view of both pagenumber and pagecount fields in the viewer. Sometimes these are shown as an hashtag (#) and sometimes these show the real value. Both cases these don't show what fields are being used in the viewer: the # can be a pagenumber, but also stand for pagecount for example. The same goes with values if these are shown instead; we can't see by a value what field it stands for. - How can we now remove fields without removing the text? It doesn't seem to be possible Concerning fields the interface looks a little primitive and needs some improvement IMHO. I would suggest something like this quick draft (see image): When 'Highlight Fields' is enabled in the menu.. - You get to see the field-names in the view next to the fields (see blue texts in the image) (if these names overlap we can always zoom in to show them fully) - You can rightclick-contextmenu --> edit field on a field to show the 'Field Chooser' for that field in order to change or remove the field-filling from the text (remove the field by setting the dropdown to 'None')