rui_mac

If we can't add new characteristics to existing tools, I hope we can, at least detect clicks/double clicks/drags/drag&drop, etc, in documents/artboards, so that we could implement new "tools".

I ask for this tool since the beta period for version 1.0.
So, it goes back to 2014. That means that I have been asking for this tool for about 9 years now.
It was one of the tools that I used often, when I used FreeHand. And it was amazing. There are lots of things that can be acheived with this type of tool
I still have hope to see it implemented.
And I know that, is Serif implements it, it will make it excellent. Much better that in Illustrator or CorelDraw.
Come on, Serif!!!!
Like Picard says... MAKE IT SO. 

I ask for this tool since the beta period for version 1.0.
So, it goes back to 2014. That means that I have been asking for this tool for about 9 years now.
It was one of the tools that I used often, when I used FreeHand. And it was amazing. There are lots of things that can be acheived with this type of tool
I still have hope to see it implemented.
And I know that, is Serif implements it, it will make it excellent. Much better that in Illustrator or CorelDraw.
Come on, Serif!!!!
Like Picard says... MAKE IT SO. 

These old posts show that this is an old request:
 
And here is a video I made showing the Blend tool behaviour in FreeHand:
 
 

I ask for this tool since the beta period for version 1.0.
So, it goes back to 2014. That means that I have been asking for this tool for about 9 years now.
It was one of the tools that I used often, when I used FreeHand. And it was amazing. There are lots of things that can be acheived with this type of tool
I still have hope to see it implemented.
And I know that, is Serif implements it, it will make it excellent. Much better that in Illustrator or CorelDraw.
Come on, Serif!!!!
Like Picard says... MAKE IT SO. 

These old posts show that this is an old request:
 
And here is a video I made showing the Blend tool behaviour in FreeHand:
 
 

I ask for this tool since the beta period for version 1.0.
So, it goes back to 2014. That means that I have been asking for this tool for about 9 years now.
It was one of the tools that I used often, when I used FreeHand. And it was amazing. There are lots of things that can be acheived with this type of tool
I still have hope to see it implemented.
And I know that, is Serif implements it, it will make it excellent. Much better that in Illustrator or CorelDraw.
Come on, Serif!!!!
Like Picard says... MAKE IT SO. 

Couldn't agree more, that's one of the reasons we've put these examples up.  However I should re-emphasise that the examples don't represent everything that's possible with scripting, even at this early stage.  It's ok to find the examples underwhelming:
Note: "just to demonstrate" and "basic"  But like I said, constructive feedback is welcomed, just don't worry that this is all you're going to get.
This next bit is mainly for any devs who might be reading this.
The Javascript API is built entirely on top of the C API.  Actually, it's built on top of a header-only C++ SDK that minimally wraps the C API so we don't have to worry about explicitly deallocating any handles that might be used.  We've not cheated and called directly into the Affinity backend from the Javascript layer, it's all going through the C++ wrappers and therefore through the public C API functions.  This is great for testing, as tests written in Javascript exercise all abstraction layers.  We will likely release the C++ headers along with the C headers.
There is a low-level Javascript API that is as similar to the C API as possible, which has the benefit of reducing the amount of documentation we have to write.  There are some differences between function signatures, but essentially they are the same, with each C function "projected" into Javascript land.  We then provide a set of JS files that wrap those exposed JS functions into ES6 classes and hide a lot of the boring boiler-plate that no-one cares about.
For maximum performance, you'd use the C or C++ layer.  For convenience, you'd use the high level JS layer, which is what the examples use. For Javascript consumers who want to design a different OOP layer, they are free to require() the API functions directly and wrap them up however they like.  I would say that as a dev coming from a mainly C/C++ background, I was surprised at how performant the Javascript levels have turned out to be.
 

To me the Illustrator-like Blend tool is the number one feature still missing. I do hope it will be in Designer rather sooner than late. Blending curves, shapes, gradients and colours would open up so much creative possibilities and speed things. There is just no way to create certain things without it.
Keeping my fingers crossed for 2023.

Tried to mimic an Illustrator tutorial. Got there because the gradient fill works with the simple spherical shape. This would have been so easy with blend tools.
Instead of manually tweaking everything: Select text and shape - blend. Rescale group and darken the fill colour - blend.

Meanwhile, FH9 is running in my SheepShaver:  

Or just good old Python like every other piece of software in the world that isn't InDesign, lol.

I have been requesting this feature since the beta stage for version 1.0
I used it a LOT in FreeHand, and I even posted some exemples of how it was done in FreeHand.
This is really a MUST HAVE!!

I have been requesting this feature since the beta stage for version 1.0
I used it a LOT in FreeHand, and I even posted some exemples of how it was done in FreeHand.
This is really a MUST HAVE!!

I have been requesting this feature since the beta stage for version 1.0
I used it a LOT in FreeHand, and I even posted some exemples of how it was done in FreeHand.
This is really a MUST HAVE!!

So much could be done with such a tool.
And I know Serif would make something wonderful.
Much better that the blend tool of Illustrator.
Come on!!! It has been asked for since Designer was in beta 

If the C API allows everything that the Javascript API does (which I would guess it probably does?) I would be prepared to write a Python library for it myself. 

I'm a loooooong time Photoshop user. And when I say "loooooooog time", I mean I started with version 1.0 of Photoshop.
Although I still have to work with Photoshop at my workplace (since the agency where I work, uses the Creative Suite), at home I use Affinity Photo (except for work having to do with intensive alpha mask work, as Photoshop is still much, much better at it).
However, I do try to transition as much as possible to Affinity Photo, for all bitmap related work (I fully transitioned to Affinity Designer for all my vector work). But I still find some things that I have to admit that Photoshop does better and the Dodge and Burn tools are some of those things.
Take a look at the attached image and tell me what you guys think.

Why was the decision made to support Javascript and not Python? I know Adobe uses Java, yet Blender, Krita, 3ds Max, Rhino, Revit, etc. all support Python. In the software I use, Python is the common denominator and Java isn't even used. Just wondering here.

I'm a loooooong time Photoshop user. And when I say "loooooooog time", I mean I started with version 1.0 of Photoshop.
Although I still have to work with Photoshop at my workplace (since the agency where I work, uses the Creative Suite), at home I use Affinity Photo (except for work having to do with intensive alpha mask work, as Photoshop is still much, much better at it).
However, I do try to transition as much as possible to Affinity Photo, for all bitmap related work (I fully transitioned to Affinity Designer for all my vector work). But I still find some things that I have to admit that Photoshop does better and the Dodge and Burn tools are some of those things.
Take a look at the attached image and tell me what you guys think.

I’m pretty sure that what you want isn’t possible at the moment but I’m also pretty sure that it’s been requested before.
(I did a quick search for paint vector and paint curve but there are too many results for me to easily go through.)
You can use certain brushes in Designer to paint along a curve/vector but Photo doesn’t have those brushes and the other functionality you mentioned doesn’t work with curves.
Here’s one thread which I found from 2016 which is asking for similar things but it’s not an actual request:
https://forum.affinity.serif.com/index.php?/topic/19670-how-to-limit-brush/

The greyscale values are just a single list of values.
A "greyscale LAYER" includes the greyscale list of values and a n opacity list of values.
All layers include an additional list of values for the opacity.
So, a greyscale LAYER is simple a set of two "greyscale" lists.
And an RGB LAYER is a set of four greyscale lists, one for Red, one for Green, one for Blue and one for opacity.
Once again, there is no excuse for the opacity list (call it alpha, or key, or mask, or opacity map, or whatever) that is merely a list of values just like a greyscale image or any of the composite channels of an RGB or CMYK image, to be treated differently.
In a nutshell, an alpha channel is exactly the same as a greyscale image and should be treated the same way, allowing all tools and operation that a greyscale image allows.

Pleeeeeeeeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaseeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!
Any language, I do not care, I just want to have it.
The reason for me is: As by no doubt there is considerable lack of programming resources at Serif, such a feature would take off quite some burden from Serif, i.e. many feature requests would vanish or never be asked for. So, I think, Serif themselves would profit the most from it.
Just to add some specific points: Join scripting with macros, i.e. macros for all programs and make macros scripts (that can be edited, not like now, which drives me crazy). And I recommend to have a well designed user forum to share and exchange macros (OK, I am old school and hope this won't be NFT macros then... 😉)

Thank you so much. I assumed that it wasn't possible because as soon as I turned off the Separate mode, all my studios that resided in my second screen were all gone.
I created a new studio configuration for my two screens now, using non-Separated mode.
Thank you so much.

I have used so many languages I've lost count, starting with Fortran on punch-cards. The "best" of these is Python for several reasons:
Low cognitive overhead: you can pick up the basics in no time. Readability: I can walk back to code written a decade ago and understand it perfectly. Adaptability: skills I learn in one domain are just as applicable to another. Popularity: there's lots of people already familiar with the syntax. Ubiquity: works on every platform. A second choice would be Javascript, which is moderately good at the above.
But nothing with the word "Apple" in it, please. Why would anyone commit to any of their products? A couple years down the line they will deprecate all your hard work.