yinYangMountain

Alfred: It worked. And, although I'm not sure, I'm guessing that's probably the method the original designers used. THANKS!

Alfred: It worked. And, although I'm not sure, I'm guessing that's probably the method the original designers used. THANKS!

Wow, thanks! I had no idea some (not all) of those frames became vertically aligned.

You can find the flow options in the "Paragraph" studio
Keep paragraph together and do not separate last lines should be selected.
 

Seems your text alignment in the text frames are set to center. Look in the context tool bar and change it to top align.
The screen shots you posted show it's set to center.
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

I have the same Toolbar bug.
Note: This same Toolbar Bug first appeared and occurs in QuarkXPress v2016. It appeared to be MacOS / Mac configuration specific and was fixed by Quark in v2017 and v2018. Their workarounds for v2016 were the same.
If Serif cannot solve this easily, they might wish to contact the engineers at Apple to see why this happens.
Current Testing Configuration: