MmmMaarten

For those working with Krita too; today I've also created a tutorial video on how to use the script to export and import Krita layers in Moho. Just updated the opening post with the video.

For those also working with Spine; Version 1.1.0 just got published. Now the script also imports the bones data if available and recreates the bone tree in Moho. See the mohoscripts page for more info about what features are supported. It's live now!

Working a lot with Moho Pro I saw myself rebuilding scenes I designed in Affinity Designer or Photo with exported images in Moho again. I never have to do that when using Spine to animate as Affinity has this great Spine JSON batch exporter in the Export Persona. So I was missing that when working in Moho. Until now; I've developed a free plugin script for Moho which let's Moho import all layers and exported cropped images from Affinity Photo and/or Designer via the exported spine.json file! For who is using both Spine and Moho, like me, it is even quite far in importing the setup pose with all images as exported from Spine too. Including all transformations of the images and even tinting of images. There are some limitations when importing spine.json files coming from Spine tho (see mohoscripts page for the script), like images which use meshes aren't supported. But the most important features are supported already! [update] Also when the spine.json file has bone data (like files exported from Spine itself, or when using special layer naming in Krita's exporter), the skeleton will be recreated in Moho during import since v1.1.0! But the main reason for making this was to import layers from Affinity tho. And that all works great now! A real time saver. It also works for Krita, Photoshop, After Effects, Gimp etc. when you install an existing export to spine.json script in Krita. The script is free to download. Downloadlink and more information is here: https://mohoscripts.com/script/wp_spine_import And here are some demo's/tutorial videos I just created. Have fun!

Beautiful!

Wow! Is the whole picture done in Designer with vectors? That's madness (in a good way)!

Excuses, excuses. Gaslighting and lying. To talk right what is criminal behaviour. As criminals always do.

There are two great initiatives with fundraisers to make a fist against these greedy exploiting companies to respect our copyrights and stop these illegal activities and theft: EU: https://gofund.me/404acacb US: https://gofund.me/2df3dc07

Stop this bullocks. If you can't design, stop stealing from artists who can and learned by putting a lot of effort in their craft. Watch the video below instead to get that you're a thief when using AI systems to generate your 'art' because you're too lazy to learn it. And for artists here: there is a way to stand up against the stealing of our art. How and why is all in the video below: https://www.youtube.com/watch?v=WMykeJm8wJI

Thanks for your response and correction. I get what you're saying and understand these are two different things and edited my post. However, it's still automatic scrolling that's not working, so it makes sense we call it that. Long story short, no matter the naming; we expect it to auto-scroll when we drag'n'move layers around (as it did before) and it doesn't. Which makes it a pain to move layers around now as we need to drag'n'move several times and manually scroll the list a little further each time, only to move items through a long list Hope Serif will fix this for the upcoming 2.2 version as it should be very high in priority to have a working layers UI IMO.

Confirmed here. I'm having the exact same issue here (layers list doesn't auto-scroll while drag'n'moving layers to before or after the visible part of the list) and was about to open a new thread until I saw this one. Working on a powerful machine here in a simple file so definitely not a speed issue. Undocking the layers panel doesn't fix it. Neither does restarting Designer. Auto-scroll is 'just' not working. Never had this issue before in v1, so I'm pretty sure this has nothing to do with the v1 issue thread. I'm not 100% sure if this was working before in v2 or not, but I never encountered this before in v2 until today. Using Affinity Designer 2.1.1. Windows 11 Pro. Please see video below. layers-panel-doesnt-autoscroll.mp4

I understand you wrote this months ago, but for what it's worth; when I look in v2 the Author field is empty (also after saving and re-opening the file), so not sure you you got a name there? Yeah, it's crazy this still isn't solved. This is such a dangerous thing while not solved, but should be so easy and quick to fix IMO

As a side thing, but directly related to the same hyperlinks panel: Another thing I would like to add as a feature request: when on url-mode Please don't add http. That's ancient, should not be used and each site should have an https anyways; so add https instead. Otherwise we still need to add the s everytime.

Not sure I follow you, but the last thing I would personally want is all urls and e-mail addresses in the text to automatically turn into hyperlinks. More often than not I would not like that. I was purely talking about the popup dialog that appears when adding a hyperlink while we have a plain text url text or e-mail address text selected in the text before hitting the 'add hyperlink' button from the hyperlinks panel.

You're right, I accidentally talked about Designer, while meaning Publisher. My bad. Nice to see it's fixed in 2.2! Coud the first point be added as a feature request? I think it would be very helpful if Affinity could detect if a link is an url or e-mail (which is pretty easy to do with a simple regular expression). If only, because when it's set to the wrong type we need to switch to the right type and when we do that Affinity clears the text box making it lose the automatically filled in selected text. Thanks in advance!

Two issues regarding e-mail addresses and hyperlinks in Affinity: 1) E-mail addres not recognised When selecting an url in text and clicking the plus-button on the hyperlink panel to make it a hyperlink, Affinity recognizes this as an url, fills in the url in the textbox, switches to the url mode and enables the OK button in that dialog box. However when we do the same with an e-mail adress in the text, it doesn't recognises the e-mail address as e-mail, but acts like it's a url. 2) Impossible to create hyperlink for perfectly valid e-mail adress with a hyphen inside (-) The ' add hyperlink' popup dialog doesn't allow e-mail addresses with a hyphen inside, although this is a perfectly (and real world) e-mail address; it doesn't disable the OK button, making it impossible to add a hyperlink on this e-mailaddress!!

Amazing work! Please keep doing what you do! (well, unless somebody forced you to do this with a gun... than get out of there as soon as you can)

@Dan C Here it is: https://www.w3resource.com/xml/prohibited-character-literals.php It says literally that the literals > and < are forbidden in the XML format (which SVG is based on), so the file is just corrupt and it would make complete sense that Affinity cannot open it for this alone. However I do think that Affinity should throw a warning when a file being imported is illegal instead of doing... uh... whatever it's doing?

@Dan C I was curious so also tried this and it's nice to see Vectorstyler can open it. However, That seems to be only because Vectorstyler is overly forgiving on the file and just handles the SVG standard at least very loose/not strict/not at all. Which could be both a good thing (it opens more) as a bad thing (it also opens rubbish files that aren't compliant to the standard). To start It looks like all IDs in the file are illegal due to the xml spec for IDs. Id's like &lt;Mesh&gt; aren't valid AFAIK. The &lt; (less than) stands for < character and &gt; (greater than) stands for the > character and that 'encrytion' doesn't make any sense in an ID to begin with, even if it would be allowed. So it looks like all IDs are wrong in this file. Which would make the SVG wrong/corrupt as it's not compatible with the XML standard to start with. Without even looking further. I have to check the standard to be 100% sure tho, but I'm pretty sure about this. This might have happened because the svg file wasn't downloaded as is, but was 'encoded' and treated as just a text document somewhere to make everything 'harmless'. Losing the functionality of the document. But even if these symbols (< and >) wouldn't be encrypted, it still wouldn't be valid IDs, so the original generated file wouldn't be valid either. So for this alone it would make absolute sense that Affinity is not buying that file. It looks like Affinity is just more strict in expecting the SVG file to match the standard. Although if this is the issue I would expect Affinity to at least throw a warning that the file is corrupt/incompatible with the xml/svg standard. <g id="321353356351 4"> <path id="&lt;Mesh&gt;" class="s0" d="m3009.8 1808.1q-514.7 0-1029.4 0 0-231.9 0-463.9 514.7 0 1029.4 0 0 232 0 463.9zm0-463.9q-514.7 0-1029.4 0 0-231.9 0-463.8 514.7 0 1029.4 0 0 231.9 0 463.8zm0-463.8q-514.7 0-1029.4 0 0-232 0-463.9 514.7 0 1029.4 0 0 231.9 0 463.9zm0-463.9q-514.7 0-1029.4 0 0-231.9 0-463.9 514.7 0 1029.4 0 0 232 0 463.9zm-1029.4 1391.6q-514.7 0-1029.3 0 0-231.9 0-463.9 514.6 0 1029.3 0 0 232 0 463.9zm0-463.9q-514.7 0-1029.3 0 0-231.9 0-463.8 514.6 0 1029.3 0 0 231.9 0 463.8zm0-463.8q-514.7 0-1029.3 0 0-232 0-463.9 514.6 0 1029.3 0 0 231.9 0 463.9zm0-463.9q-514.7 0-1029.3 0 0-231.9 0-463.9 514.6 0 1029.3 0 0 232 0 463.9zm-1029.3 1391.6q-514.7 0-1029.4 0 0-231.9 0-463.9 514.7 0 1029.4 0 0 232 0 463.9zm0-463.9q-514.7 0-1029.4 0 0-231.9 0-463.8 514.7 0 1029.4 0 0 231.9 0 463.8zm0-463.8q-514.7 0-1029.4 0 0-232 0-463.9 514.7 0 1029.4 0 0 231.9 0 463.9zm0-463.9q-514.7 0-1029.4 0 0-231.9 0-463.9 514.7 0 1029.4 0 0 232 0 463.9z"/> </g>

Thanks guys! Nice to see you like it!

BTW this was the original drawing:

Hi Folks, I had some fun time animating a drawing I made when I was 40 years ago, when I was six years old. Animation was done in Moho Pro, but I happily used Affinity Photo for making all the cutouts and doing some stamping and tricks to make it work. And of course the great export persona (I might have used Affinity Designer for that tho, as flexible as the Affinity ecosystem is in just opening the same file with another Affinity app!)! Hope you like it!

Thanks for the response and for moving this to the v2 forum! Hope it gets some traction soon!

@Callum It's juli 2023 now and we're at version 2.1.1 now and it's still not working. The issue doesn't only appear when using Krita, but now that I'm using Sketchbook Pro (v9.0.26) in Windows, it's the same with PSD's coming from there. I wouldn't think this is a very difficult thing to solve in Affinity, but it's pretty inefficient and thus frustrating to contstantly needing to rename created files. Could you please move this thread to the v2 bugs forum? And please ask the developers to fix this? Thanks in advance!

@NotMyFault Wow, that would've been the last place I would've searched. Great find. Thanks!

Hi, I have this issue quite a lot and now is the time to finally find a better workflow to do this; I have an image, masked with a rectangle that also defines the background color with it. But now I'd like to change the color of this mask object (the rectangle) because I'd like to change the background color. So far I unmask this first, change the color of the rectangle and mask it again (or change another way to do this background color anyway, but that's not the point now). But there must be a way to directly change the color of this 'mask-object' without unmasking it first, right? How to do this kind of stuff without unmasking? Hope this makes sense!