Johnnyyyy Posted May 10, 2023 Posted May 10, 2023 When I'm trying to change the line stroke width for footnotes in this documents, it just crashes every time. No idea what causes this or how to fix it....Using latest version on MACOS latest version M1 Macbook Air PACKAGE.zip Quote
MikeTO Posted May 10, 2023 Posted May 10, 2023 Hi, I've duplicated the problem with your document in 2.0.4 and with the 2.1 beta 1790 but I can't duplicate it with a fresh document. I'll try to figure out what's causing it but your footnotes seem pretty standard. Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.2, MacBook Pro 14" (M4 Pro)
MikeTO Posted May 10, 2023 Posted May 10, 2023 The problem appears to be with three images: image1.jpeg, image2.jpeg, and image3.jpeg. They're beige squares less than 1mm in each direction and don't seem to be for anything. #3 is pinned. I don't know why deleting them solves the problem, but if all three are deleted I'm able to change the note stroke thickness. To delete them, open Window > Resource Manager. Select one of them and click Locate in Document. Using the Layers panel, click the Delete icon. Repeat for each of the three images. Then save the document and try changing the note thickness. Note for Serif: in the test document, the image3 is pinned to a location in the overset text but auto flowing the text to additional pages so it's pinned normally doesn't prevent the crash. Only deleting these three images solves it. Deleting image3 on its own doesn't solve the problem. It's odd. Dan C and Johnnyyyy 2 Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.2, MacBook Pro 14" (M4 Pro)
Johnnyyyy Posted May 10, 2023 Author Posted May 10, 2023 Thanks MikeTO, great detective work No idea how these weird little images got there 😯 MikeTO 1 Quote
Dan C Posted May 11, 2023 Posted May 11, 2023 Hi @Johnnyyyy, Thanks for your report and your files provided - I can confirm that I've also been able to replicate this issue here and will get it logged with our development team now. Interestingly unpinning these images also resolves the issue, which I'll be sure to include with the development report. Out of interest, was this file imported from a different format into Publisher, or was the document created directly within the app from scratch? Many thanks in advance! 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.