Diary Generation Options : Testing / Troubleshooting

Navigation:  Scripts > Diary Generation > Diary Generation Options >

Diary Generation Options : Testing / Troubleshooting

Previous pageReturn to chapter overviewNext page

The Testing Diary Generation Options below are a miscellaneous assortment of options that are useful when testing a diary and correspond to options of the Generation Options property (Unicode) or .

 

Execute macros in the debugger

Use this option if you wish to use the macros debugger to see the step-by-step execution of any macros contained in the current script. The option below can also be used in some cases to achieve the same results.

Execute macros

with b_DEBUG = true

Use this option, along with the b_DEBUG system variable to test macros with specific code. This is often a useful substitute for the above option, when you only wish to see the result of some testing code in the final output file, not step-by-step in the debugger.

 

The Troubleshooting Diary Generation Options below are usually only used whenever you are getting unexpected results or encountering an unexpected Quark crash (a link is provided whenever a property can be used to set this option for the current script or as a default).

 

XNT Temp Files

The default value of Windows Delete should be kept except in rare cases when QuarkXPress is crashing upon closing, but after a successfull diary generation (ie. you can see the output file in the c:\temp\qpp\tmpopf\ folder and it is fine). Contact technical support if you think that you may need to use this option. This usually only happens for QuarkXPress 6, for very short diaries (fewer than 10 pages), and on very fast computers (2GHz and more). This option, is only available for QuarkXPress versions 4 and above.

Log QuarkXPress Activity

Use this option, whenever QuarkXPress crashes, to log all of the actions that Quark performed prior to crashing. This activity log can then be used in conjunction with the p-Code Viewer to identify the command that is causing Quark to crash.

Multi-Pass Execution

This option should only be used if you have a script with complex macro tokens recursion, that is causing Cannot Find Text ... errors to be generated. However, if this is the case, then you should set this property in the current script and not modify its value here in the Diary Generation Options dialog.

Page Copying Delay

A delay, inserted after the page copying stage, used to give time to QuarkXPress to re-synchronize its internal threads and structures. The default value of 1000 milliseconds is usually sufficient for most cases.


In general, the only cases when this value might need to be increased is when using QuarkXPress 6, with computers that have a fast processor (over 2GHz), and for diaries with many pages (over 100) and many textboxes (over 100 per 2 page spread), in particular if there are many objects that are grouped or locked.

OPF Transfer Delay

A delay, inserted after the diary generation is complete, but before QuarkXPress closes down, used to give time to QuarkXPress to re-synchronize its internal threads and structures. The default value of 1000 milliseconds is usually sufficient for most cases.


In general, the only cases when this value might need to be increased is when using QuarkXPress 6, with computers that have a fast processor (over 2GHz), and for diaries with few pages (less than 10) and few textboxes (the case with holidays pages or planner pages that have very few textboxes containing the results of GenTokens).

 

If you want any of the above settings values to be standard for all new script created in the future, then you can change the default values of all the diary generation options that correspond to ScriptLine Property by going to the Execution Preferences.


Topic 177215 updated on 12-May-2016.
Topic URL: http://www.qppstudio.net/webhelp/index.html?diarygenerationtestingtroubles.htm