abra100pro Posted October 26, 2023 Posted October 26, 2023 AD 2.2.1 Scaled a rectangle and expected to have the gradient of it scaled, too (makes no sense otherwise) – see images: Quote
loukash Posted October 26, 2023 Posted October 26, 2023 Works for me as expected. What exactly did you do? Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
abra100pro Posted October 26, 2023 Author Posted October 26, 2023 Hoi @loukash Funny – I tried it in a new document and could not reproduce it. I then tried the original document and it was/is still there – please find it attached. Do I oversee something?... ADRectangleGradientScale.afdesign Quote
loukash Posted October 26, 2023 Posted October 26, 2023 28 minutes ago, abra100pro said: Do I oversee something?... Nur unter uns: "oversee" ≠ übersehen etwas übersehen = miss something Anyway, something is wrong with both rectangles. Simply recreating them fixes the behavior. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
abra100pro Posted October 26, 2023 Author Posted October 26, 2023 1 hour ago, loukash said: Nur unter uns: "oversee" ≠ übersehen etwas übersehen = miss something Anyway, something is wrong with both rectangles. Simply recreating them fixes the behavior. Danke, muss mehr englisch üben! 🙂 I made these rectangles, then copies the two artboards, then moved one rectangle to another artboard and that's when I first found this strange behaviour. Quote
loukash Posted October 26, 2023 Posted October 26, 2023 1 minute ago, abra100pro said: I made these rectangles, then copies the two artboards, then moved one rectangle to another artboard and that's when I first found this strange behaviour. So to figure out if this is a bug, you may want to try to reproduce those exact steps with a new document to see if it happens again. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
abra100pro Posted October 26, 2023 Author Posted October 26, 2023 1 minute ago, loukash said: So to figure out if this is a bug, you may want to try to reproduce those exact steps with a new document to see if it happens again. well, "exact steps" sounds like a challenge 🙂 I'm gonna try some things. Quote
loukash Posted October 26, 2023 Posted October 26, 2023 Just now, abra100pro said: "exact steps" sounds like a challenge 🙂 Jaja, so ist es In other words: To qualify as a bug, an issue should be reproducible by some means. Otherwise the developers won't know what to look for. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
abra100pro Posted October 26, 2023 Author Posted October 26, 2023 3 minutes ago, loukash said: Jaja, so ist es In other words: To qualify as a bug, an issue should be reproducible by some means. Otherwise the developers won't know what to look for. of course – however, maybe the devs find something in my file that explains them what was going wrong. However, I'll see what I can do. I found out, that the gradient with the problem hadn't become a rectangle like the ones that work: Quote
Dan C Posted October 27, 2023 Posted October 27, 2023 Thanks for your report! 19 hours ago, abra100pro said: I found out, that the gradient with the problem hadn't become a rectangle like the ones that work: The 'new' Gradients shown in your screenshots above have additional handles as the Gradient has been scaled with the object. These are called 'Correction Paths' and are covered in the following helpfile page, under "Transforming objects with linear or radial gradient fills" - https://affinity.help/designer2/English.lproj/index.html?page=pages/Clr/gradientEditor.html?title=Gradient and bitmap fills You can double click on a Correction Path node to remove it from the Gradient, if they are no longer required following the scaling of the object with the Gradient applied. _____ This however doesn't exactly answer why the gradients in the original objects in your file are not scaling when transforming - as they appear to have similar properties to a newly created Gradient, though do not show the aforementioned 'Correction Paths' after scaling the rectangles, indicating the application is aware they are not being scaled. I have managed to find a fix for these specific gradients - if you select the object, the open the Fill dialog from the Context Toolbar and double click the 'End' gradient node to simply select it, the Gradient is then correctly scaled with the object and shows the 'Correction Paths' as expected: 2023-10-27 13-04-53.mp4 In my testing I've not yet been able to discover the exact reasoning behind this behaviour in your file, or a workflow to trigger this to occur with a new Gradient. If you have any further ideas as to how this file ended up in this state, please let me know and I'll be happy to log this with the team 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.