Option Clicking Text Overflow Arrow Doesn't Do Anything

[Barry Southwood]

Option clicking the overflow arrow, in the new beta version, doesn't flow the text frame to a new page based on the Master page. It doesn't do anything now. I'm on a MacBook Pro OS Sonoma 14.6.1.

Screenshot 2024-10-22 at 11.57.42 PM.pdf

[Hangman]

Hi @Barry Southwood,

This is working for me on a MacBook Pro OS Sonoma 14.6.1. for non-facing pages... For facing pages, the Option key behaves like holding the Shift Key flowing text to multiple new pages which I don't believe is supposed to happen so may be a bug in the new Beta...

[MikeTO]

8 hours ago, Hangman said:

Hi @Barry Southwood,

This is working for me on a MacBook Pro OS Sonoma 14.6.1. for non-facing pages... For facing pages, the Option key behaves like holding the Shift Key flowing text to multiple new pages which I don't believe is supposed to happen so may be a bug in the new Beta...

That's not what I'm seeing, Option is still creating just a single frame for me.

In 2.5 in a standard facing-page doc, holding Option while AutoFlowing from a right page created a single frame on a new left page. In 2.6, it creates a single frame on a new facing-page spread. It doesn't create a frame on the right page. I think this is an improvement over 2.5, it's better for AutoFlow to create spreads and not a page.

[Hangman]

14 minutes ago, MikeTO said:

That's not what I'm seeing, Option is still creating just a single frame for me.

I've assumed from @Barry Southwood's post that he's using Master Pages with Text Frames...

If the Text Frames don't appear on the Master then yes, I see the same behaviour you describe but if the text frames are based on the Master this is what I see when holding Option while AutoFlowing from a right page created a single frame...

[MikeTO]

You are correct, the Option modifier is not working for master frames.

[Affinity Info Bot]

An issue raised in this thread ("Option Clicking a Text Frame’s Flow Button Autoflows Text to Multiple Text Frames") has now been reported to the developers by the testing team (Ref: AF-4796). Thank you very much for reporting this issue to us.