thomaso

To me in V1 the status bar does not mention a right click (-> on mac: CTRL-Click). But it obviously does in Garry's video. So it appears to be a V1/V2 or a mac/win thing. – Are you able to get the double arrow cursor when hovering over a node with the Point Transform Tool? point transform status bar macV1.m4v

It does not happen to me in V1. – Can you show your workflow in a screencast, including the Canvas + Tools + Context Toolbar + Layers Panel?

See the status bar Tool tips: CTRL key -> "transform".

Thanks, @carl123, clever solution to achieve the corner radius via the Decoration's stroke width! If the fill gets set as a Paragraph Decoration, too, the Text Frame panel is not required + you can save the design as a Text Style. (…which, for a different font size, only needs to adjust the Bottom Indent if the stroke has "Scale with Object" activated.)

I can't open V2 to see how Carl did it, – nevertheless, here a workaround with a pinned object for one end of the background. It moves with typing. The Art text frame itself has a paragraph decoration as background fill colour. rounded txt frm grows.afpub

Workaround: You could export the document instead of printing it from APub, especially if you don't send an .afpub / .afpackage to the print shop. FWIW, to me APub's print dialog gets reset when APub got quit (both via usual quit and force-quit) and reopened. So possibly it helps if you empty the .autosave file(s) in your user library when APub is closed, in case they store any misleading data. BTW, because your crash report mentions Print Marks / Crop Marks in the Crashing Thread 0: Note, for N-Up with print marks I need to set the scale factor manually ('fit' and 'shrink' don't work) + I need to set in the N-Up options the Left/Right offset + H/V gaps to make the marks appear in the print dialog preview. (however, ignoring these settings doesn't cause a print crash to me and seems to be related to your macOS Sonoma, as you mentioned already).

Yes, either there, – or top right, next to the existing layer lock. To get the space for an additional icon in the top bar the text "Opacity" could get replaced by an icon + tooltip.

In addition to the mentioned hints: If you select more than 1 layer then the "Lock Children" checkbox leaves its position hidden outside the right window edge and kindly gets moved to the middle of the Context Toolbar. Luckily, it does not matter what layer types you select as long 1 layer with child is among them. So, with the Move Tool, you can simply press the shortcut for 'Select All' (cmd/Ctrl-A) to get immediate access to the wanted option. Personally the location and accessibility disturbs me since years. As an option which affects not only that layer which was selected while activating the option but affects all according parent layers if activated and since it remains active until it gets deactivated, I would expect it rather in the Layers Panel and accessible independent of a certain tool (though it affects Move Tool actions). If you like you could give this feature request of 2019 your vote … or start a new one for V2 in the according forum.

>> Alexa, ask ChatGTP for that interview & and send me a translated PDF <<

The know-how to write the code It's not much about know-how or a technical aspect of development. It appears to be more a question of marketing, customer loyalty, customer trust and experience with a tried and tested product and their consistent company. (it's still Serif, – different to e.g. Freehand or PageMaker which toggled between various companies before being quit and replaced by newer products.) Former DrawPlus customers might simply find that their product has been discontinued while the development company is offering now a new line of apps to replace it. It then seems logical for these users not to come up with the idea that the new product would offer fewer capabilities than its predecessor, but rather the same – or some more, since it was a newly developed successor.

Definitely! – Do you know how dictionaries get managed in/by Windows? As shown in the screenshots from two posts above, there are ways in macOS to influence whether a custom dictionary entry is used for a specific or all languages: with an appropriate system setting and/or by directly editing these custom dictionary files with a Text editor. Is it possible for a similar workflow to work on Windows, too – apart from the current Affinity options?

Such an "agreement" may work in this thread (where it, on the other hand, appears not necessary any more) but may fail at other spots. Thus it appears useful to use / search for the 'official', 'correct' terms (in case they exists). In former type setting with physical, 3-dimensional objects, every letter had a minimum height, defined by its material (a rectangular cuboid 'body' made of wood or). Unfortunately I could not find yet the English term(s) for the area above & below a letter that is not ascender & descender – while this area had defined a minimum leading (line spacing) for a certain letter and font. The figures below name this area in German "Kegel", "Kegelhöhe", "Achselfläche", "Schriftkegel" or "Schriftgrad" (= modern 'font size' ?), while, unfortunately in the figure it is unclear how it distinguishes from ascender and descender (does the illustrated font have capitals only?). Additionally it appears that certain letters could exceed their "Kegel" (their basic, cuboid block / 'body') which could result visually in a reduced minimum leading. With photo typesetting this area above/below a letter ("Kegel", "Kegelhöhe", "Fleisch") lost its meaning and vertically overlapping lines became possible. In digital type this area appears to be defined within a font individually and actually arbitrary as "by design", as that virtual "Default" leading which confuses in this thread.

It is possible but requires on both pages of the spread a certain ratio of paragraphs (spaces after). (-> see below). In your screenshot (named 'bgtest.png' which might mean 'baseline grid test') you have set a 'space after' of 6 but it appears you also have a baseline grid of 12 activated. The baseline grid overrides the 'space after' of 6 and thus the visually resulting space is 12, not 6, and thus the lines can match at the bottom. That is why I said on 2nd Oct. "… there is no chance (or just coincidence) that all text will be aligned at the bottom of the frames as desired." In this case "coincidence" can also be influenced by yourself, for instance if you add or remove a paragraph break to influence the bottom lines. Since every paragraph (≠ line break) will cause an additional 'space after' one paragraph more or less can make the two pages of a spread match (but, of cause, does influence the text flow on all following pages). Maybe it helps to visualize the problem with a practical example. The picture below might be sufficient to demonstrate the issue, the maths to the right is not required to understand what's happening there: A parking space is divided into multiple slots of same size (~the 'leading'), one slot for each car. If a car occupies more space than one slot (demands a 'space after') the other cars will either have to park closer to each other (reduced 'leading') or 1/2 car would be left over: However, this overlap at the bottom edge can be visually corrected if another car takes up additional space (= “space after”). Then the two "spaces after" ("paragraph breaks") ensure that no half car is left and no car overlaps ... while reducing the total number of parked cars in this way:

…the legal aspects are in discussion, for instance: https://www.mindprison.cc/p/ai-art-challenges-meaning-in-a-world https://www.europarl.europa.eu/news/en/headlines/society/20230601STO93804/eu-ai-act-first-regulation-on-artificial-intelligence

Oh, I haven't noticed your .afpub before, just the video. 8x10 Final PRESS 103123_tho.afpub P.S.: This time your video had no sound (extremely low sound). And: you can upload videos to your forum posts. Drag it to you editor or click the link below "choose files..."

To me it appears to work to edit the pressure profile of a curve that contains path text. In the pressure profile: First move both nodes to the bottom, then drag the curve in the middle upwards to create a new node. If you want to move the start/end node independently press the required modifier key (on mac it is the Option key).

Thanks, that is what @Oufti pointed out, too. On the other hand there is definitely "one default leading for the Affinity applications": It is saved in the app's "Defaults" and the Text Style "Default" / "[No Style]" where it is defined as one specific font and leading.

Do you use "generative" on purpose? It is not identical with the discussed "artificial intelligence" for image creation or automatic image background expansion based on huge data bases of existing images. While "generative" may mean "based on algorithmic formulas" it is used already in Affinity for instance for "Procedural Textures" in APh or in tools like the "Inpainting Brush". Accordingly "generative" design is common since many years, in 2D and 3D design and architecture. For instance … https://www.generativedesign.org/ http://www.generative-gestaltung.de/2/#sketches https://processing.org/books/

What "default" do you / the OP / me have in mind? I referred to that default which is stored as factory default in the apps, it is one specific font + leading. But thanks to you I must correct my previous post. Obviously I had forgotten that I customized 'my' default leading in V1 APub to 120% (= 14.4 pt) (apparently to match it the/my default of InDesign). – I did not alter this default in AD + APh + an old APub beta, where the / this default leading is 12.4 pt and not set as percentage ("% Height") but with the leading menu item "Default". So there are two terms "default": the one in the leading menu, named "Default" – versus the one in the Edit menu, named "Defaults" (plural s) while both are used for the [No style] definition "by default". Not to mention the "Default" (singular) in the Text Style panel. – Sorry for confusing them.

It is a matter of the layer type. Yes, it is quirk of affinity ("document" & "image" layers for a non-destructive workflow approach) and worth to remember. See for instance: https://forum.affinity.serif.com/index.php?/search/&q="copy pixel selection"&quick=1&sortby=relevancy&search_and_or=and https://forum.affinity.serif.com/index.php?/search/&q=copy pixel selection&quick=1&updated_after=any&sortby=relevancy&search_and_or=and

In addition to @MikeTO's hint: Words added directly to the file ~/ Library / Spelling / "Local Dictionary" (via TextEdit / macOS) work in Affinity for every language, and they can get selected as "Unlearn Spelling" from any language in Affinity. Whereas words in the custom dictionary file "de" (my system language) work in Affinity only for this language ("Deutsch"). Thus it might be more efficient or reliable to edit these specific dictionary files manually / outside Affinity.

Thank you! – Embarrassing I never tried this S: menu before, as if I haven't even seen it. Do you know where it is defined which glyph exists as 'true' sub-/superscript? In a short test it's obviously font dependent but also appears confusing in comparison with the Glyph Browser:

This two sentences seem to contradict. The fact that we can't find an item in the file system doesn't necessarily mean that the item does not exist. <-> As you seem to experience yourself, this profile appears to be available for Affinity. For instance it could be stored 'hidden' as temporary item in one of its proprietary file formats. In my understanding it is required and rather efficient that at least basic profile data get stored within the Affinity documents: For instance to have them available when the document gets used on a different computer – e.g. a print service – that does not have this profile installed. Furthermore it seems to be required to store at least two profiles within the document in case the user switched while working between RGB and CMYK and back with the Assign option used. Test: create a new document, -> switch its colour space, don't change the displayed profile, -> note the profiles of both colour spaces. -–> Then change your app colour preferences to quite different profiles. –> Create another new document and compare the two profiles again. The question whether Affinity documents contain profiles was discussed a while ago in this long thread (initiated by different file sizes of empty documents): https://forum.affinity.serif.com/index.php?/topic/185363-empty-document-file-size/

Is this a result of your experience – or a guess what the OP possibly might mean? If a word gets identified as wrong in a language though the word is not part of that language, then – I assume – the word did not got the correct language assigned in the layout. Dictionaries containing several languages would not be useful since there exist various words that may exist in several languages, while some of them may have a different spelling in a certain language. (e.g. disc / disk / disque )