Not sure if this adds much of anything, but here are some notes I've kept on this topic:
<h2>Tracing ACL execution</h2>
There is little to no formal documentation of how to run ACL traces under the editor. Primarily information on how to do it was gleaned from posts to the adepters forum on ptcuser.org.
-
- You can use the a "
That is, on the editor's command line, to direct trace output to a different location than the default of an editor popup window, you can enter a command like:
-
- "
-
- For editor 6.0, it was located under folder path "
-
- For versions of the editor prior to 6.0, it was located under folder path "
-
-
-or-
- " filename;" where you substitute a valid file system path (no blanks) for the " filename". Specifying a " filename" will direct output to that file. Here's an example: "
-
-
- You can use the a "
-
- "
-
-
For reference, the following information was found in a copy of the "Arbortext® Styler™ User's Guide" under the major topic of "Performance Profiling for Arbortext Styler
or FOSI Stylesheets:"
How to Output Diagnostic Information
In general, diagnostic information can be output to a nominated file using the command line instruction set debug=diagnostic type,=filename,
where:
-
- diagnostic type is the type of information you wish to output, either a full set of those available or a specific type (see Diagnostic information types for a list of types)
-
- filename is the absolute path to the file where the diagnostic information will be written. The filename must not contain spaces.
-
The debug instruction is usually activated via the Arbortext Editor command line while the document that appears to contain a problem is open. Note, though, that if you are trying to find out why a document is slow to open, the instruction must be given before the document opens to have any effect.
<h2></h2>
In Reply to Jason Buss:
Bless you, kind sirs...
When adepters goes quiet for more than a couple of days, I start to wonder if there's a holiday I missed out on...
