Segar Posted December 29, 2022 Share Posted December 29, 2022 Affinify Publisher 2.03 MacOS 13.0.1 Hardware Acceleration: On.Brief Explanation: When a second endnote is created after a first (later in the text), the footnote text for footnote 1 is erroneously moved to footnote 2. Steps to reproduce: Create new document. Create text frame and populate with 'Once upon a time'. Position text cursor at end of 'Once' in the text frame. View Notes panel. View End Notes tab. Click 'Insert Note' icon. 'Endnotes' frame appears on new page. Drag the 'Endnotes' frame back below the original text frame. Set Note Position to 'Separate Frame' ('Endnotes' frame erroneously jumps back to where it was ... ... but drag it back to the first page again) Populate footnote 1 with 'One'. Position text cursor at end of 'upon' in the original text frame. Click 'Insert Note' icon. Footnote 2 is created. Text for footnote 1 should stay with footnote one ... ... but instead the text for footnote 1 is now attached to footnote 2. end note defect.afpub Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted December 29, 2022 Share Posted December 29, 2022 Welcome to the Serif Affinity forums. You created the text for endnote 1 improperly. It belongs between the blue [] marks. Edit: If I remember correctly, Publisher will have left the cursor there for you to start typing. You've apparently repositioned the cursor to be outside the brackets, then added the text. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Segar Posted December 29, 2022 Author Share Posted December 29, 2022 Ah! I understand ... and yes, it works for me now. Thank you for the clarification. [Maybe not great UI design though! I can imagine why it was coded to be like this ... but I'm not convinced it's the best solution from a usability perspective ... be interesting to see how many other people find it confusing] Thanks again 🙂 walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
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.