Dazmondo77 Posted September 5, 2018 Share Posted September 5, 2018 I'm having trouble with column breaks in a multipage document. first off the standard mac shortcut 'numpad enter' doesn't seem to work (I've now changed to cmd numpad enter) now it works here and there but theres the odd column where I want to flush some text at the bottom of a column into the next column and it skips the column - I've tried this with and without text flow options enabled and it doesn't seem to make a difference Mac Pro Cheese-grater (Early 2009) 2.93 GHz 6-Core Intel Xeon 48 GB 1333 MHz DDR3 ECC Ram, Sapphire Pulse Radeon RX 580 8GB GDDR5, Ugee 19" Graphics Tablet Monitor Triple boot via OCLP 1.2.1 - Mac OS Monterey 12.7.1, Sonoma 14.1.1 and Mojave 10.14.6 Affinity Publisher, Designer and Photo 1.10.5 - 2.2.1 www.bingercreative.co.uk Link to comment Share on other sites More sharing options...
Chris_K Posted September 13, 2018 Share Posted September 13, 2018 Hi Dazmodo77 Do you have a file you can provide that displays this at all for us to take a look at? Cheers Serif Europe Ltd - Check the latest news at www.affinity.serif.com Link to comment Share on other sites More sharing options...
KEC Posted September 17, 2018 Share Posted September 17, 2018 Here is a file that demonstrates the issue (I think). When I try to insert a column break before the "Engine & Transmission" heading, it causes the text to jump below the end of the second column, rather than to the top of the second column. At least, that's the behavior I expected. Insert Column Break.afpub Link to comment Share on other sites More sharing options...
Staff MEB Posted September 17, 2018 Staff Share Posted September 17, 2018 Hi KEC, Welcome to Affinity Forums Go to the Topic Heading style (edit), Paragraph > Flow section and set Keep with next X lines to 0 (zero). It should then behave as you want. A Guide to Learning Affinity Software Link to comment Share on other sites More sharing options...
KEC Posted September 18, 2018 Share Posted September 18, 2018 It certainly does. Thank you for pointing out what was wrong. My error, to be sure. (Sorry...) Would you be kind enough to explain why this happens? I hope I'm not being too daft, but I would think it would work this way even if "Keep with next" were set to a number greater than zero. Link to comment Share on other sites More sharing options...
Staff MEB Posted September 18, 2018 Staff Share Posted September 18, 2018 Hi KEC, I also believe that changing the Keep with next setting shouldn't affect this. I've passed this issue to the dev team and will get back to you as soon as I have some news. A Guide to Learning Affinity Software Link to comment Share on other sites More sharing options...
Recommended Posts