LEB Posted January 7, 2024 Posted January 7, 2024 I found the following reproducible bug. Edit a text style where the baseline [Fr : ligne de base] is non-null positive, x Click on the little arrow on the right to increase the value by an increment Publisher will first switch the value to (-x)+1, instead of x+1 garrettm30 1 Quote
walt.farrell Posted January 7, 2024 Posted January 7, 2024 What measurement units are you using? 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 January 7, 2024 Posted January 7, 2024 I can reproduce this bug on macOS. Here's a screen recording. It doesn't happen with the regular baseline field, just with the text style one. Screen Recording 2024-01-07 at 10.24.36 AM.mov garrettm30 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)
Staff Callum Posted January 8, 2024 Staff Posted January 8, 2024 Hi All, I have logged this with our developers to be fixed Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
LEB Posted January 9, 2024 Author Posted January 9, 2024 Many thanks for having logged the bug, and for @MikeTO for having produced the video. Quote
Staff Affinity Info Bot Posted March 11, 2024 Staff Posted March 11, 2024 The issue "Edit Text Style - Position & Transform baseline jumps to negative value" (REF: AF-1691) has been fixed by the developers in internal build "2.5.0.2317". 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 @Affinity Info Bot to notify us. LEB 1 Quote
garrettm30 Posted March 22, 2024 Posted March 22, 2024 6 hours ago, LEB said: Many thanks! And many thanks to you as well as @MikeTO for bringing this bug forward. This is one of the bugs I have encountered from time to time but didn’t have a chance to report because I just had to get my work done. LEB 1 Quote
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.