My document just sits there.

   Many customers who are not yet familiar with the 'flow' of document assembly with Pathagoras will begin a document assembly project by recalling the source text onto the editing screen. And the document just 'sits there.'

   That, of course, is the way they undertook a project in 'pre-Pathagoras' times. We need to 'break' you of that habit.

   When you recall the original document, the text remains static until you do something to cause a change.  That is on purpose. It is not a design flaw. Pathagoras thinks that you recalled the text to the screen because you want to edit it. It is waiting for you to do something.

  Never use the source text for active document assembly. Use the source text only to correct a typo or to add additional automation features.

   Why? It simply is too easy to accidentally overwrite the original when you start a document assembly session with a source document. In view of that, Pathagoras requires that you 'assemble' your document to get the benefit of the program's automated features.

   When you assemble your documents using the tools that Pathagoras provides, the process is active and automatic. Any <<*Options/Optional/Repeats*>> blocks present in the source text are 'processed' as you desire. You end up with a 'perfect' initial draft, just what you were looking for.

You know that you are looking at an assembled document because 'Document 1', 'Document 2', etc. shows at the top of the editing screen, indicating a new document -- one that you cannot accidentally overwrite the original if you press 'Save'.

You know that you are looking at the 'source' document because its name shows at the top of the editing screen.

   Does that mean you cannot test your work on the original text. No, but be careful not to 'save' your work after testing. See this page for more information on pure testing.