IthinkthereforeIam

I'm procrastinating and browsing a few threads. I hope you don't mind I'm commenting on your post. I don't want to seem obsessed with a public rodmap, but I don't quite understand the rationale for not revealing a draft of the new features for the next few releases. You're at beta 2.4, so you could mention what the developers are working on for say the next two or three versions (making it clear that you're not bound to these roadmap previews).
 If you're still a long way from v.3, you could even consider a longer-term roadmap, without compromising your primary objective of selling licenses... so you may avoid a fraction of repeated requests for new features, questions for knowing what is coming next, etc. 🙂 I think you'd rather read a good novel (or even Shakespeare's classics) than numerous posts on this forum (new spiral tool :  😵‍💫)

I'm procrastinating and browsing a few threads. I hope you don't mind I'm commenting on your post. I don't want to seem obsessed with a public rodmap, but I don't quite understand the rationale for not revealing a draft of the new features for the next few releases. You're at beta 2.4, so you could mention what the developers are working on for say the next two or three versions (making it clear that you're not bound to these roadmap previews).
 If you're still a long way from v.3, you could even consider a longer-term roadmap, without compromising your primary objective of selling licenses... so you may avoid a fraction of repeated requests for new features, questions for knowing what is coming next, etc. 🙂 I think you'd rather read a good novel (or even Shakespeare's classics) than numerous posts on this forum (new spiral tool :  😵‍💫)

You're right, it's never easy to communicate (at all levels) and indeed, I remember reading on more than one occasion that adding such a feature was "the simplest thing to do, and that it should be so easy that it should already be done!"... I talk enough with developers (my sons) to realise that it's clearly not simple to add a new feature to a program that has already become so complex. In fact, they say that it's not normal for a program (or part of) to work straight away 🙂

It's not always wise to communicate all those things, as it often then tends to additional demands/requests and everyone jumps in then want's this and that being added etc. Add to that, that most feature demanding users also don't have any real clues about development procedures, it's complexity (difficulty levels 1-12), possible unwanted sideeffects, needed format changes and the general impact for certain demands here. So what can be realistically done fast and painless, in contrast to very complex (possible more error prone) extensions.
I take one often demanded example here, namely bitmap-to-vector tracing, which no need to ask is genarally a valuable feature always to have and offer. BUT adding such a feature is by no way a trivial task to do. All better already available (to some degree reusable) tracing algorithms aren't freely available/reusable, as all the better realy good ones do come along with license fees for their reusage in comercial software. And not all algorithms here do support good quality color tracing, or features like center-line tracing etc. Then adding own color detection and quantisation to a plain on B&W operating algorithm is also no trivial task. ... And so on ...
Thus I said, it always depends.
Or according to Murphy's law (which is an aphorism about human error or sources of error in complex systems) which states: “Anything that can go wrong will go wrong.” 😉

"may differ" indeed and I have no doubt about your wisdom and the sincerity of your thoughts... I did add "in my humble opinion" and I'm not on this forum to start new endless polemics about what was or should be. Thanks but no...

Nope, as I initially said, there have been nothing added/done in this direction.

And in particular, from the 2.1 enhancements in that What's New list:

I doubt that, otherwise it would have been mentioned in some version changes thread.

Not absolutely sure if I completely understand what you concreate mean here, but in case you meant that subcategories can be taken over ("copy/pasted/somehow be shared" etc.) from one main category into another different main category here, no that's AFAIK not possible (...at least not in v1 apps).

Just as a touch of humour, here's a photo I found edited with APh v1 some time ago, just modified for the occasion (text & liquify applied to the head):
 

Just as a touch of humour, here's a photo I found edited with APh v1 some time ago, just modified for the occasion (text & liquify applied to the head):
 

I used Affinity Designer.
I used the Transform panel to accurately place the wheels, setting the numbers to be centred on the centre spot of the lower edge of the bounding box, so that the wheels each sat on the (unshown) rails.
I made the body of the locomotive by starting with an ellipse, converting to curves, then I used the node tool to delete the lower centre point, then I made the two end points to become sharp corners. Then I added a point to make the back of the tender. I lined everything up using numbers entered into the Transform panel.
I made the smoke from ellipses, gradually making them bigger and longer to try to show that the locomotive is running at speed and that the smoke dissipates, then using various levels of opacity to indicate the dissipation of the smoke.
I realize that doing the smoke that way could not, as far as I know, be done with a real linocut, so I am thinking of trying to have another version where the smoke dissipation is done with white swirls that gradually have thinner white lines farther apart.
I made the wheels first, then lowered the body of the locomotive all in one piece onto them after designing it further up the canvas. I grouped it all, then I added the black rectangle and moved it to the back then I coloured the locomotive and its smoke white.
As I drew the picture I saved what I had done in case I made a mistake and had to go back.
William
 

Wow, so knowledgeable customers are kept down and in the dark at the lowest common denominator thanks to fumbling beginners installing all sorts of fonts and LUTs and brushes and what not. The goal as a software provider should be to solve the problem, not create a variation of it.
Make thumbnail preview default Let an algorithm disable LUT thumbnails if it seems there are many LUTs installed. Then show a warning and explanation - let the customer decide if it should be enabled Make it a setting also in preferences This approach is one I've seen in several programs. Sanctions only when there's a reason, and even then, choice.
It's too unserious to completely remove it from the product, only to possibly reinstate it later, or perhaps not, while the customer has no idea what's happening or when something might happen.

I did, sort of. I effectively asked them not to tag staff who are not currently interacting in the thread. Clearly sometimes it helps in order to indicate who you're replying to. 
As head of the testing team I often know about unreleased features, but as head of the testing team it's not my job to say what features are planned or how they are progressing so I'll not be changing that approach here

Vectorstyler also does this very well. I don't usually have to adjust it much. 

Just as a touch of humour, here's a photo I found edited with APh v1 some time ago, just modified for the occasion (text & liquify applied to the head):
 

[Updated Nov 30 2023 - new version for Publisher 2.3 with 120 more pages than the first version]
Learn how to format text and publish books and other long documents with Affinity Publisher 2.3. This free in-depth manual is filled with steps, tips, and recommendations for:
Character and paragraph formatting - added Nov 30 Text styles - added Nov 30 Documents, Pages, Master Pages, Sections, and Baseline Grid Text Frames, Text Flow, and Stories Books and Chapters Cross-References, Table of Contents, and Index Notes - including Footnotes, Sidenotes, and Endnotes Fields - including Page Numbering, Running Headers, and Custom Variables Anchors and Hyperlinks Printing and Exporting Settings This manual does not cover objects and photos so it covers approximately half of the topics.
Updated version:
Publisher Manual Nov 29 2023.pdf
 
Q&A
Is there a full manual I can purchase? No, this is all there is. Is this really free? Yes, I'm making it available free of charge. It's copyrighted to prevent others from publishing it as their own. Is there an iPad version? No, the steps and screenshots are for the macOS and Windows versions. Is there a version for Designer or Photo? No, but the text features are largely the same so you may find it useful. Why does it use a print layout if it's a PDF? It's a demonstration of how to use the features it describes to create a print book. Original version:
Publisher Manual Sep 26 2023.pdf
Publisher Manual Sep 18 2023.pdf

A little Monster

A Little Monster
Added a small asset collection from Santa Baby (Does not need to be!)
Vector Configurations of the Little Monster and associated vector.
Files as displayed
AD 2.3 File not asset library!
 




Little Monsters Toolkit.zip
 
 

Hi,
I would like to suggest adding a Path Width Tool for easier and more precise stroke adjustments. This tool would allow users to thicken the outline at specific points by simply clicking and dragging with the mouse. Other software like Adobe Illustrator and Amadine have a stroke width tool.
The current method, using the Pressure chart in the Stroke panel, is not as user-friendly or accurate as it could be.
 
Current method:

Suggested (like Amadine or Adobe Illustrator):

 
 

Original black and white image is "Stonethwaite Bridge, Borrowdale, Cumberland, from a soft ground etching by William Green, 1809," now in the public domain, courtesy of the British Library.
The bluebird and cardinal, who is actually bright red in my original jpg, are regulars from my garden. They join me in wishing everybody a much happier 2024!!