This appears to be working fine for me, and I have attached a simple test to demonstrate what I am doing. This test project uses extremely simple settings, really all we are doing here that is unusual is adding a heading to the section that is printing text. No formatting override is being performed. The zip file also includes the two output files as compiled on my system.
…I would have to artificially split up each document into two parts and assign a section type to the solution part such that a page break will be placed at its beginning in the compile process. A lot of complexity for a relatively simple task.
I suppose you could look at it that way. To my mind anything so large as a page break makes sense in its own outline node, because it is a decidedly different thing than anything around it. I would have a setup like this, with section types denoted in brackets:
Quiz Section A [Quiz Section]
What is the price of tea in China? [Question]
The pot calling the kettle black. [Solution]
Quiz Section B [Quiz Section]
Now one could create a document template folder structure that is the quiz section group, with the two subdocuments nested within it, section types all set up and ready to go, and the group view mode on the container locked to Scrivenings. Click on the quiz section; see text in editor just like you’d normally be working.
Only difference being you wouldn’t have invisible codes somewhere in the file to carefully work around in order to not accidentally delete them.
Just a thought! We do put the command in there for those that prefer a less structural approach to document design—but I would say the above is definitely more aligned with the design intent of the software.
The attached project demonstrates how I would approach this. You’ll find that if you click on the “Quiz Section” template folder the two subsections will appear in the main editor, ready to edit. If you wanted to test this, you could select the draft and insert this folder from the
Project ▸ New from Template ▸ submenu.
manual_page_break_test.zip (177.7 KB)
Also: I noticed that some of the manual page breaks mysteriously disappear over time. I can’t reproduce that yet, but will keep an eye for finding what exactly caused them to disappear. Did anybody run into that yet?
Haven’t seen that happen, but I’m definitely the wrong person to ask.