bbrother Posted January 19, 2024 Posted January 19, 2024 App: APub version 2.3.1 OS: Windows 10 Pro (22H2 compilation 19045.3930) Hardware Acceleration: OFF The problem(bug): Problem 1: As you can see in the attached video the bounding box of picture frame isn't updated correctly after resizing it or moving it when "lock children" is aplied. To force an update of the bounding box to the correct sizeneed do deselect the picture frame and select it agin. Problem 2: Don't untick the "lock children" and delete the picture frame with image inside it. Create new blank (no image inside) picture frame. - this picture frame inherits the "lock children" setting and the bug with bounding box size despite there is no children in that frame. - you can't turn of "lock children" in that blank picture frame because this option doesn't show up in context toolbar in the move tool for empty picture frames. Only solution is temporary place an image and turn of "lock children" to ged rid of that bug. (Attached video with the problem) APub_boundig_box_lock_children_bug.mp4 Quote
Dan C Posted January 19, 2024 Posted January 19, 2024 Thanks for your report @bbrother! 3 hours ago, bbrother said: Problem 1: As you can see in the attached video the bounding box of picture frame isn't updated correctly after resizing it or moving it when "lock children" is aplied. To force an update of the bounding box to the correct sizeneed do deselect the picture frame and select it agin. I can confirm this issue is already logged with our development team and appears as though it should hopefully be resolved in an upcoming beta build. 3 hours ago, bbrother said: Problem 2: Don't untick the "lock children" and delete the picture frame with image inside it. Create new blank (no image inside) picture frame. - this picture frame inherits the "lock children" setting and the bug with bounding box size despite there is no children in that frame. - you can't turn of "lock children" in that blank picture frame because this option doesn't show up in context toolbar in the move tool for empty picture frames. Only solution is temporary place an image and turn of "lock children" to ged rid of that This issue isn't currently logged with the team, though I suspect the above fix may also resolve this issue. I'll be sure to log this with the team for further testing when the above issue is resolved in an internal beta build, and if not it will remain as a separate report to be resolved. I hope this helps Quote
bbrother Posted January 19, 2024 Author Posted January 19, 2024 Thank you. @Dan C in the context of Problem 2, the question arises whether it is a good idea for each change to the photo frame attribute to be remembered (inherited by the newly created frame). This is what object styles should be for. Dan C 1 Quote
Dan C Posted January 19, 2024 Posted January 19, 2024 2 minutes ago, bbrother said: the question arises whether it is a good idea for each change to the photo frame attribute to be remembered (inherited by the newly created frame). Agreed, I have actually raised this as part of the bug report to be considered by the team - personally I understand why the next picture frame retains the settings of the last one drawn/deleted, as the same is true with other tools in Affinity; Quote However I have noted that we should then offer the 'Lock Children' context toolbar option with an empty picture frame, so the user can disable this after drawing the frame, without having to add an image within the frame to access the controls. In either case, our dev team should confirm which behaviour they expect and adjust the app as such Quote
Staff Affinity Info Bot Posted January 26, 2024 Staff Posted January 26, 2024 The issue "Bounding Box shows incorrectly on a resized picture frame when using 'Lock Children'" (REF: AF-1757) has been fixed by the developers in internal build "2.4.0.2252". 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.