MmmMaarten

It's done with Spine

@Alfred Yeah, I think so too. I didn't make any assumption tho, that's why there's clearly an ? after 'woman'. I did that even on purpose just to prevent sensitive feelings if it wasn't a guy to leave it open. @Dan C It wasn't even banter. But guess these days people don't understand HUMOR anymore. I'll leave humor out of this forum from now on. And I won't post any more in this thread.

Wow, what's with the hate? You obviously completely misunderstood my post which was nothing more than lighthearted and a little humor. Nothing personal nor offensive in my post in any way. I even liked your post, so totally miss why you react so overly offensive and sensitive. So the one making bad assumptions is you. Try to read and understand someones post before reacting like this and relax.

Poor ducks. Just relaxing there in the sun while some dude woman? (mrs in your name) curls their world

Normally I always work with Wacom (intuos), but today I was working with mouse on a Surface Book 2 (not used the touch/pen screen), no wacom connected. [Edit] I don't believe this has anything to do with using mouse vs wacom pen. And if it would happen once every 20 minutes I would definitely have posted sooner about it. It's a pretty crazy thing I don't see any logic of besides there seems to be some screen re-draw / recache or similar issue.

@stokerg did you see the video? They're already gone when switching to the move tool and back. This is independent of using a mouse or pen. I've seen this both when drawing with mouse (like today) and with Wacom tablet (most probably the previous stills I've included above).

And it's not one of the actual handles, 'cause they are in a completely different spot:

I just made a screenrecording; when you drag the canvas the 'dot' (handle or node) moves with it. When switching from Node-tool to Move-tool and back it's gone: affinity-handle-or-node-issue.mp4

@stokerg I've just had another one a second ago. It looks like it's not the node, but the handle. I'm not sure tho, it could as well be an illusion that it's smaller because it's on a different background. When it appeared at first it was connected to the path in some unexpected way, but after undo, the connectionline (the handle line?) dissapeared and this circle stayed. This is what's left: And this is a reconstruction how >> I Think << it looked right before undoing (not sure where it was connected to the path, but it was in an unexpected spot, not set by hand

Not sure when exactly this happens, but it happened to me a lot since the last or fore-last upgrade of Designer (it was definitely not happening before that, so introduced in one of these two upgrades). I was waiting for posting this in hopes to find out when this happens to give you more info, but couldn't find any logical connection or cause so far after months, so figured you guys should know about this by now, if not already mentioned by somebody else. I've searched the forum for this, but couldn't find a simular issue. Pretty sure it was the 1.10.5 version that introduced this, but else it's the version before that (I've used all versions). Issue: sometimes while drawing with the pen (or editing a path/curve?) 'floating vertices/nodes' appear. So nodes/vertices that aren't connected to any path. They appear on placed where the cursor (AFAIK) never've been and aren't logical to me either. I made some screenshots when this happened:

Thanks for the @Alfred. I didn't even know that it was possible/enabled on this forum 😀

Yeah, if you see a duck, you see a duck. I saw it too when you mentioned it. I didn't want to change the grayscale of the front or back of that guy tho, as it's always supposed to be exactly this gray scale completely. Otherwise it would've been clearer what the front and back arms were.

@DWright wow, never knew that. thanks. Looks like that label (or artist) used it for their record(s): Sorry for asking in your topic @Vaclav Slovacek, back ontopic again now!

Just a side-question out of interest as I keep wondering @DWright; the logo in your avatar looks familiar; are you perhaps a drum'n'bass head (knowing you're from the UK might make that plausible)? (Isn't that a DNB-label? Or is that only my interpretation after years of being a DNB dj?!)

Thanks @EmT. Glad to see it's being picked up!

@jmwellborn Haha, thanks! 😅 Yeah, this was a real fun short one to make. BTW the pilot is not a duck... it's the guy from my logo 😀 -->

It's over 30 Degrees Celsius indoors now (no airco, all windows blacked out), but outside it was today even hotter and tropical.... so I decided to practise some more animation today in hot, but dry air as an excercise All graphics happily created with Affinity Designer!

Sometimes, eventhough Spine is selected as Batch builder, no spine.json file is created when exporting slices. I have to watch more closely when exactly this happens, but I'm pretty sure this is what happens: - Have a file, create slices, select Spine batch export and export the slices (spine.json gets created just fine) - Keep Affinity open and start creating a new file, create slices and go to the slices tab in the export persona: now 'Spine' is still selected as batch exporter, but it doesn't use this batch exporter when exporting the slices. It only seems to work if we manually set/refresh the batch export selection by moving to another setting in the dropdown first and than re-select Spine in the dropdown again. So it looks like the batch export method is set to 'none' when creating a new file, but the UI for it wasn't updated, so it still shows 'Spine' while in reality it's set to 'none'. This is obviously confusing and prone to errors.

@AdamStanislav Yeah, time is moving fast (faster when you're older)! Sad to read you had to move because of a fire, hope everybody's alright and you managed to save the most important things.

@AdamStanislav yeah, we're animals without a doubt. Just another animal species with our own pros and cons compared to other animals. That's why it's such an interesting podcast series. I think it's interesting they seriously talked about animal rights to include in our legal systems, because of our growing awareness of the fact that other animals also feel, can be lonely, need love, play, remember, want company, raise and protect their children, want to fit in a group, deserve their freedom etc.. Like the idea that an animal who passes the mirror test (understanding to see yourself in a mirror), like an elphant could (at least some), could get a lawyer or even vote to fight his rights like humans can. Not exactly like adult human beings and clearly not for all animals (equally), but more compared to little children who do have rights in our system. It's pretty crazy that animals, in our Dutch legal system at least, aren't treated like animals in our legal systems, but literally called and treated like objects. That's weird, especially because we ourselves are animals too. I think that's a very interesting subject and good to see there are actually (scientific and in other areas) people thinking about these kind of topics, because it's crazy only humans have rights in 'our' system and we treat other animals, which are all family and we are strongly related, more than we tend to think, like objects and slaves. That's as weird as that we had humans as slaves in the past (and still in some places). BTW I think a lot of 'our own animal species' are acting very much like vegetables at the moment. But this is not the place to get political and I don't want to either. Also, I'm no activist or vegan or whatever, but I am fascinated by this, it made me think after listening to that podcast (and hope others too) and think these scientists have very valid points. But so far for now about this subject from my side on the Affinity forum (especially in a 'share your work' forum)

I was inspired by a scientific podcast which does series on particular themes. This time about 'Are human beings animals' where in particular an episode about animal rights and lawyers for animals was very interesting. And had a few ideas in my head to tell a story with 3 colors and one image:

@StuartRc Looks like a fun and great project for you to gain new knowledge with for future projects! Keep up the great work!

Please guys, it doesn't help anybody if you post a reaction to somebodies feedback **to Serif**. Especially if you're not even reading nor understanding the posters post. Because if you did you wouldn't twist my words and talk about things the feedback isn't even about. It's all clearly in the first post and I even repeated it in other words. This is not the question forum, nor meant to discuss about, this is the forum made for feedback **to serif**. If it would be that Serif isn't understanding the post or has questions about it I'm happy to answer or clear things up, but it's feedback **to serif** and it doesn't help if people jump in and make clear things foggy by talking about things the feedback isn't even about. Thank you for your understanding. And hopefully Serif actually reads feedback.

@Old Bruce Guess we have to agree to dissagree strongly. Without text in the master page you cannot see what you're doing obviously and Lorem Ipsum exists for a clear reason. Also this is a template, so there is prewritten text that will be changed when used on a page. Which I think is a pretty normal use case. Besides all this; whether or not we're adding text to a master page or not or whatever workflow you or I like to use is beyond the point of this feedback to Serif. Point I'm making is pretty clear I think; it doesn't make any sense to warn a user with a bunch of spelling errors when exporting if there are NO spelling errors in the export. Hard to discuss about that I'd say.

To Serif: Hi, To my surprise when exporting pages to pdf I'm getting preflight warnings with all kinds of spelling issues. Looking where they appear they all appear in the used master page. But these warnings are redundant as all these text fields' content is overwritten in the pages themselves and the master pages only contain dummy text and/or templates, so spelling isn't important on these master pages. So to me this check doesn't make sense while exporting the final pages. It would be better IMO if Affinity would only check and warn about misspellings on actual used text when exporting, not text that is overwritten by the pages. Thanks in advance!