Seikilos Posted October 23, 2022 Posted October 23, 2022 Hi there, i was trying to create a table of figures. There are 19 images in my book and these images have a textbox with them where a certain style is set. These images + textboxes with style are grouped and then pinned. Now these groups are pinned to text. When I am creating a table of figures with the table of contents tool I do get only the figure text styles in all text frames which are either not pinned grouped or not a group at all Are there some workarounds for that? Pinned group. Unpinned group Quote Affinity User on Windows 11
walt.farrell Posted October 23, 2022 Posted October 23, 2022 I see the same behavior, but I don't know if it's a bug or just the way it's designed. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Seikilos Posted October 23, 2022 Author Posted October 23, 2022 25 minutes ago, walt.farrell said: I see the same behavior, but I don't know if it's a bug or just the way it's designed. Thanks for the reproduction. I probably will have to create this toc by hand for now Quote Affinity User on Windows 11
MikeTO Posted October 23, 2022 Posted October 23, 2022 I'm not seeing this. I put three text frames on a page formatted with Heading 1, Orange, Apple, and Pear. Orange was freestanding, Apple was pinned (floated) to another text frame and Pear was grouped with a rectangle before being pinned (floated) to another text frame. Then I put one more text frame on the page, sent it to the back since this was a test doc with the TOC on the same page as the other headings so it needed to be at the bottom of the stack. Inserted a TOC and I all three showed up in the TOC. Here's my test doc to look at. test toc.afpub If you want to have some fun, select the pinned text frames and change them to inline and then update the TOC. That's not a good idea. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
walt.farrell Posted October 23, 2022 Posted October 23, 2022 20 minutes ago, MikeTO said: I'm not seeing this. I put three text frames on a page formatted with Heading 1, Orange, Apple, and Pear. Orange was freestanding, Apple was pinned (floated) to another text frame and Pear was grouped with a rectangle before being pinned (floated) to another text frame. Then I put one more text frame on the page, sent it to the back since this was a test doc with the TOC on the same page as the other headings so it needed to be at the bottom of the stack. Inserted a TOC and I all three showed up in the TOC. Thanks, but you've done something different. We want Pear (and possibly Apple) to show up in the TOC. Or, in the case of this test document, "Heading 2a" should appear in the TOC: Grouped-Pinned-TOC-issue.afpub Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
MikeTO Posted October 23, 2022 Posted October 23, 2022 3 hours ago, walt.farrell said: Thanks, but you've done something different. We want Pear (and possibly Apple) to show up in the TOC. Or, in the case of this test document, "Heading 2a" should appear in the TOC: Grouped-Pinned-TOC-issue.afpub Didn't we do the same thing? Apple and Pear both show up in my TOC. Pear is a heading in a text frame grouped with another object and pinned (floated) in some regular text. Mine shows up and yours doesn't and I'm not sure why... Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
MikeTO Posted October 23, 2022 Posted October 23, 2022 2 minutes ago, MikeTO said: Didn't we do the same thing? Apple and Pear both show up in my TOC. Pear is a heading in a text frame grouped with another object and pinned (floated) in some regular text. Mine shows up and yours doesn't and I'm not sure why... Oh ignore that, I see what I did now. User fail. walt.farrell 1 Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
MikeTO Posted October 23, 2022 Posted October 23, 2022 So the only way around this is to pin the image and caption separately. It's funny that the TOC will pick up the heading when it's pinned and when it's in a group but not when it's in a pinned group. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
walt.farrell Posted October 23, 2022 Posted October 23, 2022 I agree, Mike. Definitely odd behavior. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Seikilos Posted October 24, 2022 Author Posted October 24, 2022 8 hours ago, MikeTO said: So the only way around this is to pin the image and caption separately. It's funny that the TOC will pick up the heading when it's pinned and when it's in a group but not when it's in a pinned group. I have already trouble pinning grouped image + text frames in a way that flows properly. Breaking the group seems like something that will tripple the manual work: Ensure text and image are separately but correctly placed in relation to the pin, then ensure that the distances of all text boxes remain consistent to the image frames and then check whether all those figure texts are correctly generated in a TOC. As a work-around I thought about group pinning, then ungroup, then generate TOC, then group again. And repeat this every single time something moves. Finally I will have to check the page numbers at the end of the workflow anyway. Since this final, manual check will always remain, I've chosen the easiest approach for me: Use the table of figures that word generated for me and manually set the page numbers at the end of my workflow. Since I have to do this for sections anyway, there is already an error-prone workflow established so checking page numbers for images becomes just another manual workflow to-do item. Typesetting a book really hits all the corners, where APub has not yet reached maturity. 😅 Quote Affinity User on Windows 11
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.