Pšenda

Just to be sure: Are you talking about having difficulty reading, for example, Defaults and Settings in your screenshot?
Or about the other entries? The other entries are grayed-out as they are currently inactive, because you have no document open.

Affinity does not yet have this tool.
https://www.google.com/search?q=Blend+Tool+site:https://forum.affinity.serif.com

Example file? - if is this only your problem or in principle.
 
Yes.  Unfortunately, nothing is written about printing in the text of the post.

https://affinity.help/designer2/English.lproj/pages/DesignAids/grids_axonometric.html

https://affinity.help/designer2/English.lproj/pages/DesignAids/grids_axonometric.html

https://affinity.help/designer2/English.lproj/pages/DesignAids/grids_axonometric.html

That's exactly how it is. Why is the created artboard displayed as a rectangle? Because all newly created documents have a rectangular shape. Sure, the developers could change the object name to Artboard. But honestly, whether rectangle or artboard is displayed is as uninteresting as the news that a sack of rice has fallen over in China.

Since Serif is already busy with the core software, and since a DAM is intended as a general cataloguing system, wouldn't it make more sense to ask to one's preferred DAM's developer to add compatibility with Affinity files?
Paolo
 

You're right - my error.

Yes, because this Help is for APublisher version 2 (see help path "...help/publisher2/...).
 
Yes, because this Help is for APublisher version 1 (see help path "...help/publisher/...).

Thank you so much!
Exactly what I need. Thanks again. 
 
Mark

... or that it was requested a long time ago 🙂

While I do not disagree with this specific request (to remember that setting, most likely for a particular document), I do feel a need to point out that just because something is requested multiple times, does not mean it is a good idea.  People frequently ask for things they would later come to regret, which would cause problems for someone else, or which would get in the way of even better things they may not have thought of when making the request.

Many thanks for your thorough advice on this.

Indicating hierarchy with vertical lines is a fairly standard way to express and control (see Walt's note) indentation in complex hierarchical structures - thanks for implementing them. Unfortunately, Serif used the least clear and comprehensible variant.
This is how it is handled, for example, in a development environment to indicate a hierarchy in a program code.

Edit:
 

At the launch of the Affinity product, Serif stated that the functions will be added gradually, as it is not a mere "renaming" of the legacy Plus applications (they were only for Windows, by the way), but completely "new" applications with a completely different architecture, which, among other things, allows for the support of three OS, a universal file format allowing them to be shared by all applications, and StudioLink-type functionality.

A small tip for using Google search here on the forum, which very often provides relevant results even when a "general" query is entered.
https://www.google.com/search?q=magenta+outline+site:https://forum.affinity.serif.com

I agree. Affinity 2.x initialising a document with a nonsensical 0 DPI in any circumstance is a bug.
Affinity 1.x (on macOS at least), sensibly uses a default of 72 when there is no meaningful DPI value in a JPEG's metadata.
Both Affinity 1.x and 2.x (on macOS at least) assume a default of 72 as the 'original DPI' of the problem JPEG when it is placed in a document.
 

Hello - a slightly different problem and the possibility of improvement.
If I want to use a smiley when writing a post, I am offered its text description and explanation.

After using a smiley (🤫), its meaning is no longer displayed to the reader, which is quite a shame given the incomprehensible nature of some specific smileys.
In the case of automatically replaced text with brackets, the original text and thus also the meaning of the smiley will be displayed.

Apparently an attempt at a humorous remark to get ChatGPT to generate the corresponding program code.
Edit: Perhaps the author of the proposal could generate applications functionally identical to ASuite - it shouldn't be a problem after all 😉

Please indicate their resolution (ie how many pixels they have), the DPI size is not important. As OP write, the target resolution of his image is 2993 x 7703 pixels, and they will remain whatever the DPI is. For a JPEG file, the DPI value is just an entry in the metadata. 

Yes, I had to "get used to" the changes, not that I had to "learn" them - i.e. read help, watch tutorial videos, or write questions on the forum.
You didn't understand the difference between a checkbox and a dot for controlling layer visibility, and you had to "learn" it?
You didn't understand that the Studio control was moved to another menu folder, but did you have to "learn"?
You didn't understand the change of icons, and you had to "learn" their meaning? (P.S. unknown tool icons have a Hint/Tooltip so it will tell you the name of the tool very easily. As well as layer types and their icons, which in the default/unnamed state is also displayed in the layer name).
Then yes, the transition to V2 must have been very difficult for you, and you had to spend hours on the Internet and in Help. Fortunately, I really had no problem with it.

As a V1 user, I didn't have to learn anything at all when switching to V2. That is, apart from completely new functions, which is true for every version (even V1 got new functions, which if I wanted to use, I had to learn them). 

I added to the post, which you may have misread.