Gear maker Posted May 14, 2023 Posted May 14, 2023 I have seen some issues with the Transform origin that were cured in AD 1724. I am running AD 1790 on a mac 27" 2020 with Ventura. I find that if I select one layer I can accurately position the origin. But if I select more than one layer the origin does not remain where it is dropped. It ends up jumping down and to the left of the drop point. Attached is a video and the test AD file. TransformOrigin3.mov Temp 1.afdesign Quote iMac (27-inch, Late 2009) with macOS Sierra
Old Bruce Posted May 14, 2023 Posted May 14, 2023 I bet this is down to selecting 2 separate layers with 2 separate Transform Origins plus they are both rotated. This may be okay if you Group the two layers. PetervL and Hangman 2 Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
Gear maker Posted May 14, 2023 Author Posted May 14, 2023 10 hours ago, Old Bruce said: I bet this is down to selecting 2 separate layers with 2 separate Transform Origins plus they are both rotated. This may be okay if you Group the two layers. I had found that if I selected the crosshairs object also than the Origin worked correctly. Except that I didn't want them rotated. FYI in version 1 and 2 (2.0.4) this jump does not occur. It's only in the beta. With the two Ellipses grouped it does work. But it shows another oddity, if the two ellipses are made not visible inside the group then the Origin disappears. Though if the group is made invisible the Origin remains visible. But I see that that has been the case in version 1 and 2. Quote iMac (27-inch, Late 2009) with macOS Sierra
Staff Affinity Info Bot Posted August 14, 2023 Staff Posted August 14, 2023 The issue "Transform Origin with multiple Group selections cause the Origin to become offset after the first rotation, further transforms of the origin point do not work as expected." (REF: AFD-6606) has been fixed by the developers in internal build "2.2.0.1951". 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
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.