draupnir Posted September 19, 2021 Share Posted September 19, 2021 AffPub 1.10.1 under macOS 10.15.7 I have created a table of contents and would like to have the page numbers at 85 mm with fill character dot (.). But it does not work. The underscore works. What can this be? BTW: Why is it not possible to use any character as a fill character? – draupnir Bildverzeichnis-Extern.afpub Quote Link to comment Share on other sites More sharing options...
Optische Ausrichtung Posted September 19, 2021 Share Posted September 19, 2021 23 minutes ago, draupnir said: BTW: Why is it not possible to use any character as a fill character? With Affinity Publisher 1.10.1 it is possible ... click on the "…"-Button marked with the red "x". Quote Ich hoffe, ich erlebe es noch, dass die deutschen Anführungszeichen in Affinity Publisher korrekt funktionieren. Link to comment Share on other sites More sharing options...
draupnir Posted September 19, 2021 Author Share Posted September 19, 2021 Thanks for your answer. In my version of AfPub 1.10.1 (Apple Mac Store version) I can't enter any character in (A) 😞 I tried it with a new start of AfPub and in a new document. No success. Quote Link to comment Share on other sites More sharing options...
Optische Ausrichtung Posted September 19, 2021 Share Posted September 19, 2021 17 minutes ago, draupnir said: AfPub 1.10.1 (Apple Mac Store version) Maybe that is the reason. I use the non-AppStore version for Mac. Unfortunately, I have not found a solution for the main problem. Edit: I suspect this is a program error. How would one report such a guess to Affinity without having to say everything again? Quote Ich hoffe, ich erlebe es noch, dass die deutschen Anführungszeichen in Affinity Publisher korrekt funktionieren. Link to comment Share on other sites More sharing options...
walt.farrell Posted September 19, 2021 Share Posted September 19, 2021 1 hour ago, Optische Ausrichtung said: Edit: I suspect this is a program error. How would one report such a guess to Affinity without having to say everything again? This is already in the Publisher Bugs section of the forums, so you have reported it. You just need to wait for it to reach the top of the stack for processing by the Serif staff. Optische Ausrichtung 1 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...
thomaso Posted September 25, 2021 Share Posted September 25, 2021 On 9/19/2021 at 11:52 AM, draupnir said: Thanks for your answer. In my version of AfPub 1.10.1 (Apple Mac Store version) I can't enter any character in (A) 😞 Same to me in a non-Apple but Serif-Store version. @Optische Ausrichtung, your screenshot shows the Paragraph panel. It seems the Text Style Editor dialog doesn't have text input enabled for that field (and for the decimal field either) – whereas it works in the according fields of the Paragraph panel. By the way, it reminds me to a related issue concerning text input excluding non-ASCII characters, which still appears to be broken: Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
thomaso Posted October 2, 2021 Share Posted October 2, 2021 By the way, the OP's issue appears to be already reported, logged by @Pauls and tagged (afb-4577) Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted October 18, 2023 Staff Share Posted October 18, 2023 The issue "[macOS] Text Style Panel - numeric entry for colour values in sliders not possible" (REF: AF-204) has been fixed by the developers in internal build "2.3.0.2083". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. 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.