thomaso Posted May 14, 2020 Posted May 14, 2020 I notice a few odd issues when applying Master B with replacing Master A but migrating its content. Both masters are independent. 1 of 2 picture frames appears visually as expected. Its frame has same size and position on both masters. The picture frame of the new master at this position isn't transferred (~ replacing the former) but replaced with the existing of master A. The other picture frame becomes – set to invisible, – scaled in width, – its image gets horizontally moved (~ centered to the new frame width) For all of these actions I can't understand the reasons. I would expect both picture frames of A to remain as they are (= migrated) + and get additionally all frames of B + the empty, unused frames of A deleted (= replaced). master replace existing w pict-frms.m4v Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Staff Gabe Posted May 14, 2020 Staff Posted May 14, 2020 Hey @thomaso, I can't replicate this in the latest beta. Can you confirm this please? Screen Recording 2020-05-14 at 13.35.50.mp4 Quote
thomaso Posted May 14, 2020 Author Posted May 14, 2020 Wow! In Beta 651 it works like a charm and even auto-migrates accordingly to layout variants between two masters. I am really impressed, it appears close to "Smart Master Pages" without their need of manually named layers and resources! master replace existing w pict-frms_beta651.m4v (NOTE: Since the beta usually handles former file versions as well, one should know that it seems not to work in this case: If I use my .afpub from v183 then beta 651 causes exactly the same issues. So, I need to recreate the layout to get the advantages of this improvement.) Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Staff Gabe Posted May 14, 2020 Staff Posted May 14, 2020 Any chance you can attach the file please? Quote
thomaso Posted May 14, 2020 Author Posted May 14, 2020 v183 fotobook.afpub Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
thomaso Posted May 14, 2020 Author Posted May 14, 2020 Does it mean you too get the issue with this file (though it is simple, almost empty)? Any info what may cause it there? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Staff Gabe Posted May 15, 2020 Staff Posted May 15, 2020 Yep. I get the issue too, with this file. I believe this is one of those fixes where we have fixed the cause of the problem in app (so one can't create those files anymore), but files created in previous versions still suffer from the problem. 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.