anweid Posted July 5, 2021 Share Posted July 5, 2021 The German Affinity Publisher 1.10.0.1098 for Windows reliably destroys existing layouts (saved with previous versions) under the following circumstances: In a multi-page document, insert some graphics (or table or whatever) and pin it as a character to flow with the text. In order for the image to be displayed properly, do not use a fixed line height, but keep the automatically determined one. In previous versions of Publisher, this works reliable ('BreakOK.png'). In the new beta, if any such image-containing paragraph begins at the top of a page, the image is moved to a wrong position, and the layout of the rest of the document is destroyed accordingly ('BreakBug.png'). Please find attached also the original document saved with version 1.9.2.1035 (which version 1.9.4.x could also properly read). It would be nice if the original correct behaviour could be restored. Andreas Weidner BreakBug.afpub sfriedberg 1 Link to comment Share on other sites More sharing options...
Staff Gabe Posted July 5, 2021 Staff Share Posted July 5, 2021 Hi @anweid, Thanks for spotting this. we are aware of it and it has already been logged with our developers. Link to comment Share on other sites More sharing options...
sfriedberg Posted July 7, 2021 Share Posted July 7, 2021 Oh, good. I had pointed out similar/same issues with pinned content at the top of the page in the original 1098 announcement thread and was getting ready to start a new thread on the topic, since I hadn't spotted an acknowledgement. Glad it's known! Link to comment Share on other sites More sharing options...
Staff Gabe Posted July 7, 2021 Staff Share Posted July 7, 2021 42 minutes ago, sfriedberg said: I had pointed out similar/same issues with pinned content at the top of the page in the original 1098 announcement thread and was getting ready to start a new thread on the topic, since I hadn't spotted an acknowledgement All bugs should be reported in a new thread and not in the announcement thread... Link to comment Share on other sites More sharing options...
sfriedberg Posted July 16, 2021 Share Posted July 16, 2021 1.10.0.1109 (Beta) fixes this problem for me. MikeTO 1 Link to comment Share on other sites More sharing options...
Recommended Posts