joe_l Posted August 28 Share Posted August 28 1. Set up document with mm as unit. 2. Now change the unit on the ruler corner to px. 3. Add an element an give a text wrap. 4. Type 4 mm into one field. 5. Change the unit on the ruler corner back to mm. Now there are 1,28 mm in the field. Skipping step 2 and step 5 and switching the units from the ruler corner shows the correct values. I am definitely missing something here, woke up too early. 🤦♂️ Quote ---------- Windows 10 / 11, Complete Suite Retail and Beta Link to comment Share on other sites More sharing options...
Hangman Posted August 28 Share Posted August 28 Hi @joe_l, The only way that would happen is if you changed the document dpi from 96 dpi to 300 dpi after Step 4... i.e., before changing the units back to mm in Step 5... In which case this would be the correct behaviour... Text Wrap.mp4 Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
joe_l Posted August 28 Author Share Posted August 28 3 minutes ago, Hangman said: The only way that would happen is if you changed the document dpi from 96 dpi to 300 dpi after Step 4 No. Document dpi was not touched. Quote ---------- Windows 10 / 11, Complete Suite Retail and Beta Link to comment Share on other sites More sharing options...
Hangman Posted August 28 Share Posted August 28 Just now, joe_l said: No. Document dpi was not touched. Could you make a quick screen recording as there must be a step missing in the process... If I follow your steps without changing the document dpi switching the units back to mm still shows 4 mm on both Windows and Mac (for me at least)... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
joe_l Posted August 28 Author Share Posted August 28 17 minutes ago, Hangman said: Could you make a quick screen recording as there must be a step missing in the process... Looks more like a slide show ... sorry. unit-conversion.mp4 Quote ---------- Windows 10 / 11, Complete Suite Retail and Beta Link to comment Share on other sites More sharing options...
Hangman Posted August 28 Share Posted August 28 On 8/28/2024 at 10:40 AM, joe_l said: Looks more like a slide show ... sorry. No problem... This appears to be a bug on Windows... When entering 4 mm in the Top text entry field, because you have a 300 dpi document the value should change from 15.1 px to 47.2 px (which it does on Mac)... The value you see after hitting the enter or tab key, i.e., 15.1 px isn't 4 mm, it's 1.28 mm when translated from px at 300 dpi which is why you see what you see... 25.4 mm = 300 px 1.0 mm = 300 / 25.4 = 11.811 px 4.0 mm = 11.811 x 4 = 47.2 px This is how it looks on Mac and how it should work on Windows Text Wrap v2.mp4 joe_l 1 Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
walt.farrell Posted August 29 Share Posted August 29 I see that same behavior (works on macOS, fails on Windows), too, @Hangman. I think on Windows it's assuming 96 DPI rather than using the true document DPI. 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Hangman Posted August 29 Share Posted August 29 11 minutes ago, walt.farrell said: I think on Windows it's assuming 96 DPI rather than using the true document DPI. Except that Windows correctly translates units in other areas of the UI, e.g., try the same exercise using both a 72 dpi and a 300 dpi document with Paragraph Spacing, say Left Indent... Change the document from mm to px and you'll see the following: 72 dpi Document - Left Indent Enter 4 mm and it's correctly translated to 11.3385 px 25.4 mm = 72 px 1.0 mm = 72 / 25.4 = 2.8346 px 4.0 mm = 2.834645 x 4 = 11.3385 px 300 dpi Document - Left Indent Enter 4 mm and it's correctly translated to 47.2440 px 25.4 mm = 300 px 1.0 mm = 300 / 25.4 = 11.8110 px 4.0 mm = 11.8110 x 4 = 47.2440 px Switch both documents back to mm and the left indent for both shows 4 mm Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
walt.farrell Posted August 29 Share Posted August 29 3 minutes ago, Hangman said: Except that Windows correctly translates units in other areas of the UI, e.g., try the same exercise using both a 72 dpi and a 300 dpi document with Paragraph Spacing, say Left Indent... But for this specific case (Text Wrap Settings), I'm seeing calculations based on 96 DPI on Windows when typing non-px units into the fields, when the document is set to px units. It's wrong, whatever it's doing. Hangman 1 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Hangman Posted August 29 Share Posted August 29 2 minutes ago, walt.farrell said: But for this specific case (Text Wrap Settings), I'm seeing calculations based on 96 DPI on Windows when typing non-px units into the fields, when the document is set to px units. It's wrong, whatever it's doing. I've just rechecked and you're not wrong, it is indeed based on 96 dpi regardless of the document's dpi so definitely wrong... walt.farrell 1 Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
Staff Callum Posted September 6 Staff Share Posted September 6 Hi All, I have logged this with our developers to be fixed and will update this thread once I have more info. Thanks C Hangman 1 Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
Hangman Posted September 6 Share Posted September 6 Thanks @Callum... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted October 22 Staff Share Posted October 22 The issue "[Win] Text wrapping unit conversion incorrect" (REF: AF-4226) has been fixed by the developers in the latest beta build (2.6.0.2805). The fix 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. 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.