gbXML - Debug Mode|
There are two debug modes built into gbXML. In both cases, the Tokens and Tokens2
textboxes are replaced by a single textbox, in which debug information is placed.
The debug mode can be selected using the Options > Debug Mode menu options.
In Validity Debug Mode, information is presented which shows where an invalid reference
has been entered in the validscope and inhertifrom attributes. See the help section on
Dirty XML for more information.
Each line item in the Validity display consists of four parts:
- Language - which language
- Tokenset - which tokenset
- Type - which type of invalid reference was found (validscope or inheritfrom)
- Value - the value of the invalid reference (name of tokenset that does not exist)
Most of the subroutines in gbXML are written so that when the Trace Debug Mode is turned on,
a listing is made of the sequence in which routines are accessed. Generally this will only
be useful in reporting problems to the program author to help track down where in code errors
The listing under Trace Debug Mode is cumulative - each new action adds to the list.
Double-clicking on the listing textbox will clear the list so that the trace of the next
action will be found at the top of the trace textbox.