1.8.0.502 Flow Options > Justify Vertically anomaly

[ETC]

Possible bug:

As it is now in the Release Version (1.7.3) and the Beta (1.8.0.502) if you have Paragraph > Flow Options > "Justify Vertically" turned on and the text flows from text frame 1 to text frame 2 and you would have an orphan without "Prevent widowed last lines", the text at the bottom of the first text frame does not go to the bottom as it should to be "justified vertically." If you shut off "Prevent widowed last lines", the text is justified vertically as it should be, but now you've got a widowed last line at the top of the next text frame.

I don't want to put the file up publicly, but I'd be happy to share it with developers. Is there an address to which I could send a link so the developers only can download the file and check it?

Or maybe they can just duplicate the problem themselves without my file.

[A_B_C]

Hi ETC,

I am not sure, but maybe you misunderstood to what the “widows/orphans” terminology refers. In Publisher, it doesn’t refer to text frames, but to paragraphs.

• That means, when you select “Prevent orphaned first lines” for a paragraph, Publisher will make sure that the first line of this paragraph isn’t left alone in the last line of a text frame, but kept together with the rest of the paragraph and moved to the next frame in the text frame chain.
• On the other hand, when you select “Prevent widowed last lines” for a paragraph, Publisher will make sure that the last line of this paragraph doesn’t appear alone in the first line of a text frame.

As far as I can see, the mechanism does also work with vertically centered text. See my video. Maybe I am missing your point. I am not sure whether you are after something else.

Alex 

[ETC]

To the best of my understanding, I understood and understand both settings. They aren't working as expected - i.e., on my machine with this file they are not working as you describe. That's why I would like to privately send a file to the devs. If there were an easy way to insert Lorem Ipsum in the entire document with various width letters randomly replacing letters of similar width (so the general "size" of the text remained similar), I'd do that and upload a sample file. (Nisus Writer Pro for Mac has a nice macro to anonymize text that way for submitting to support; love it!).

I'll await the devs. Or the next beta.

[A_B_C]

Okay, that sounds very strange. Please know that I didn’t mean to question your report or your knowledge, but just make sure that we have the same understanding. Seems I also misread “Justify vertically” as “Center vertically” … sorry … 

I think I can reproduce some aspect of your findings now.

[Old Bruce]

You have 3 paragraphs after that one and they are all vertically justified. I replaced all the Paragraphs (four of them) with a column break, it is that tiny blue angle after the "recusundae." at the bottom of the left column.

[A_B_C]

Thank you. You are right. I got some wires crossed. Removed the document not to create more confusion. 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.