Andreas S

Hi @Andreas S,
Just to let you know I've logged the crash when applying the Master Page with the Developers.
I'll also get the issue with the picture frame claiming to be on the Master logged, once I've confirmed it's not already logged as I'm sure I've seen this happen before.

Hi @Andreas S,
Glad to hear the file no longer crashes once you've unpinned 'Hat-House'...
You will need to edit the Master Page elements on that page so you can move the 'Stocking_Frame' group outside the Master Page elements. That way it won't 'vanish' when you apply the A4 Master...

Unpin.mp4

Hi @Andreas S,
Many thanks for the images...
The crash is caused by the pinned image on Page 7, i.e., 'Hat-House-8.jpg'. When you unpin the image and then apply the 'neues Kapitel A4' Master to Pages 6 and 7 the file doesn't crash...
The other image on Page 7, 'Stocking_Frame.jpg', is also a little odd in as much that the picture frame is locked indicating it appears on the 'neues Kapitel' Master but it doesn't so you need to right-click the Master Parent Layer on Page 7, select Edit Detached and Move the 'Stocking_Frame.jpg' and associated Caption group so it appears outside the Master Page elements, i.e., move it above or below the unpinned 'Hat-House-8.jpg' group which now also appears outside the Master Page elements on Pages 6 and 7, otherwise when you apply the 'neues Kapitel A4' Master to Pages 6 and 7, that image vanishes...
Hit the green Finish button at the top of the viewport and then when you apply the 'neues Kapitel A4' Master to Pages 6 and 7 it no longer causes the file to crash and you can resize and reposition elements as required...
Hopefully, that all makes sense, let us know whether or not this works for you...

This allows to add master pages on top 
 

Pretty easy to find alternatives for Zapf Dingbats which will work in Affinity Glyph Browser.
ITC Zapf Dingbats Std - Adobe (2007) (AFF11) - OpenType-PS - (Unicode)
(from Adobe Font Folio 11.1)
Zapf Dingbats BQ - Berthold (2004) - OpenType-TT
(three fonts - Zapf Dingbats 100, 200, and 300)
Zapf Dingbats BT - Bitstream (1993) - TTF - (Unicode PUA)
(in the old BitStream 500 Fonts CD)
 

Hi Dan,
after the comments from Old Bruce and Walt I checked on the Adobe Website and learned that Type 1 is officially discontinued since 2023. So I believe, the correct handling in the Glyph Browser would be a "nice to have" with a low priority. I'm sending you the Type 1 files anyway.
 
ZD_____.PFB ZD_____.PFM

You will probably find other issues in Publisher, if you use those fonts enough.

Thanks to all for your efforts. This explains what Designer is doing.

Yes, it agrees and tells me "triangle".
The triangle is on artboard2 in the lower right corner
Eine Seerose2.afdesign

I find some of these complaints in regard to update costs somewhat baffling.
8 years ago the first version of Affinity Designer was released. 7 years ago Photo. 3 years ago Publisher.
Throughout that time customers received free updates and upgrades, and many new users purchased the software at a reduced special offer price. I am one of those.
All the free updates actually made me feel I ought to ask Serif to charge me MORE, because the cost for V1 in relation to its functionality was always greatly in favour of its feature set. In short: very inexpensive for what was on offer.
V2 is a new release of Affinity. It is offered again at small cost compared to other commercial alternatives. V1 continues to run and isn't 'taken away'. There is no subscription. Unlike companies such as Adobe, older versions are not removed from the user's installation options. Serif's business model is based on the "you pay for it, you have an unlimited license" approach, which is actively abandoned by most other software companies.
Yet: like it or not, Serif has to generate revenue to cover development costs. They can't forever keep leaning on bringing in new users. The Affinity devs have always stated that free updates would be available for V1.xx. They stated unequivocally that V2.XX would become a paid upgrade.
Now, I understand that if a user purchased the software in the last 3 months, having to pay for a full upgrade is understandably inconvenient, and it would have been perhaps preferable for Serif to handle those cases differently.
But surely enough, at SOME point Serif has to make SOME money, otherwise business becomes untenable and they'll go bankrupt. Right?
Or perhaps Serif has a good reason to go down the subscription route after all: even IF you try with your best intentions to provide professional-level design software at a very affordable price level, AND offer 50% off to everyone at release time, STILL people complain about it.
If I were them, the subscription business model suddenly is beginning to look quite attractive. Because there is no use in trying to please everyone anyway.
PS I do agree that a grace period of 1 year or so to fix critical bugs in V1 would have been good to have and alleviate part of the complaints made.

Maybe he found the translation for "vehicles" in Monty Python's dictionary - remember "My hovercraft is full of eels"

Maybe he found the translation for "vehicles" in Monty Python's dictionary - remember "My hovercraft is full of eels"

Hi both,
I will get this issue logged. 

What @Old Bruce showed looks more like an Index than a TOC, to me. A single multi-level index could also work, with (for example) parent topic names like "1. Something", "2. Another thing", etc. where the numbers would determine the order of the parent topics in the index.
(However, you can only have 1 index in a document, so if you need both a TOC and an Index I think you need to use Bruce's approach.)

I am trying to figure out what you want. Is this what you want to achieve?
You have three levels of difficulty, Simple, Moderate and Hard. You want to have a ToC with all the listings for 

Simple 
    this._____________________ 12
    that._____________________ 15
    and another one._________ 32 
Moderate 
    some stuff. ______________ 11
    other stuff. ______________ 16
    final stuff. _______________ 24
    
Hard
    example. _________________ 5
    exercise. _________________ 17
    something. _______________ 89
    
Am I close? If so then I think you need to have three sets of Paragraph Styles which are identical except for their names and then you have to set up three ToCs.

You have to check "Ignore Text Wraps" on the text frame with the coloured text. You can see this on the Text frame panel.

Thanks, that was an easy  solution (when you know, where to click )👍

Wish XMP implementation for batch raw processing.
It will make compatible the Raw develop persona with LRtimelapse and Adobe Camera Raw / Lightroom

True, for size and position you need Master Pages. But Styles cover everything else.
Also, Assets are useful. Make a Text Frame like you like it (in terms of properties except position) and save it as an Asset. When you need another frame, just drage it from the Assets panel. Then all you need is to set the position, which you might do with Guides set on a Master Page.

I'm not sure what the "missing features" are. If you were to start with a Master Page, instead of your unstructured approach, then everything would work as you desire from the beginning, wouldn't it?
By the way, you can add a Style from a Text Frame by selecting the frame, then in the Styles panel use the hamburger (settings) menu to "Add Style from Selection". That will pick up the Text Frame properties along with the font, font size, etc. You can then apply that Style to another Text Frame (which should be empty at the time if you don't also want to change the characteristics of the text within the frame).