wguibrow.gml

开放源码的编译器open watcom 1.6.0版的源代码

all source files that make up the database file.
Each source file in the list has a check box.
An X in this box indicates that all symbols defined in the source file
will be displayed.
Click in the check box of the source file you want to disable.
This removes the X.
The blank box indicates that any symbols defined in the
source file will not be displayed.
Alternatively, use the up and down arrow keys to select the source file
you wish to disable.
Press the space bar to disable the currently selected source file.
To re-enable the source file,
click in the check box again or press the space bar.
This places an X in the box again.
.np
The
.us Pattern
section of the dialog, allows you to specify wild card directory
specifications for files.
Any symbols defined in these files will be displayed in the global
views.
For example, specifying
.fi d:\watcom\h\*.h
and pressing the
.us Exclude
button, will prevent any symbol defined in any file in the
.fi d:\watcom\h
directory with extension ".h" from being displayed.
To display symbols from these files again, specify the same pattern
and press the
.us Include
button.
.np
Pressing the
.us Set All
button displays all symbols in all files.
.np
Pressing the
.us Clear All
button causes no symbols to be displayed.
This is useful, for example, if you wish to only display symbols
defined in files in the current directory.
Simply press the
.us Clear All
button, specify
.fi *.*
in the Pattern section, and press the
.us Include
button.
.*
.endlevel
.*
.endlevel
.*
.section Enumerator Styles
.*
.np
.ix 'enumeration styles'
.ix '&br' 'enumeration styles'
Selecting
.us Enumeration Styles
from the
.us Options
menu displays the
.us Enumeration Styles
dialog.
This dialog allows you to specify the format for displaying enumeration
constants in the detail views for enumeration constants.
.figure *depth='1.37' *scale=56 *file='brow16' Specify enumerator styles for detail views of enumerator constants using the Enumeration Styles dialog.
.*
.section Member Filters for Classes
.*
.np
.ix '&br' 'member filters for class details'
.ix 'class details' 'member filters'
.us Member Filters
in the
.us Options
menu allows you to specify the members you want to appear in the
detail view of a class.
For example, you may not want the detail class to contain private
members.
Alternatively, you may only wish to see function members and not data
members.
.begstep
.step Choose
.us Member Filters
from the
.us Options
menu.
.result
This opens the
.us Member Filters
dialog where you specify the information you want
to appear in detail views for classes.
.figure *depth='2.30' *scale=52 *file='brow17' Use the Member Filters dialog to select the information to appear in detail views for classes.
.step Choose the inheritance level
from the
.us Inherited Members
section of the dialog.
.result
The options are:
.begpoint $break
.point None
Do not show inherited members.
.point Visible
Show the local members of a class and visible members of inherited
classes.
.point All
Show all local and inherited members of a class.
.endpoint
.step Click on the check boxes
in the
.us Access Level
section of the dialog to select the desired access levels.
.result
The options are Public, Protected, and Private.
Only members with the selected
attributes will appear in the detail view for a class.
.step Select the desired members
in the
.us Members
section of the dialog.
.result
Show data members in a class by enabling the
.us variables
check box.
When the
.us variables
check box is enabled, you may also enable or disable static data
members by clicking on the
.us static
check box.
.np
Show function members in a class by enabling the
.us functions
check box.
When the
.us functions
check box is enabled, you may also enable or disable static and virtual
function members by clicking on the
.us static
and
.us virtual
check boxes.
.step Click on OK
to accept the member filter query.
.result
This closes the dialog and returns you to the active window.
.endstep
.begnote
.mnote Note:
The Default button on the Member Filter dialog resets the query
to the default settings.
.endnote
.*
.section Auto-arranging of Graph Views
.*
.np
.ix '&br' 'auto-arranging the graph view'
.ix 'graph views' 'auto-arranging'
When collapsing a graph view, nodes that become hidden are replaced by
gaps in the graph.
.us Arrange Graph
in the
.us Tree
menu compacts the graph view to remove the spaces left vacant by
hidden nodes.
.np
When enabled,
.us Graph Auto-arrange
of the
.us Options
menu causes the &br to automatically compact the graph view each time
you perform a collapse operation.
To enable the automatic compaction of the graph view after a collapse
operation, select
.us Graph Auto-arrange
from the
.us Options
menu.
A check mark appears beside the menu item when it is enabled.
Select the menu item again to disable it.
.*
.section Line Drawing Method for Graph Views
.*
.np
.us Graph Square Lines
in the
.us Options
menu allows you to select the type of line that connects the nodes in
a graph view.
The default is to connect nodes of the graph using diagonal lines.
Choosing
.us Graph Square Lines
from the
.us Options
menu causes nodes to be connected using square lines (combinations of
vertical and horizontal lines).
A check mark beside the menu item indicates this method of drawing
lines is enabled.
To disable this option, select it again.
.figure *depth='2.83' *scale=51 *file='brow18' The Graph Square Lines option changes the connecting lines from diagonal to square.
.*
.section Changing the Graph Orientation
.*
.np
.ix '&br' 'change graph orientation'
In the
.us Options
menu you can select whether the trees on the graph view grow
horizontally or vertically.
A graph view that grows horizontally is one where the root node is at
the left and the leaf nodes at the right.
A graph view that grows vertically is one where the root node is at the
top and the leaf nodes at the bottom.
By default, graphs grow vertically.
.np
Select
.us Graph Horizontal
from the
.us Options
menu to change the graph orientation to horizontal.
Selecting this option changes the menu item name to
.us Graph Horizontal
in the
.us Options
menu.
Select this menu item to change the graph orientation back to
vertical.
.figure *depth='2.83' *scale=51 *file='brow19' The Graph Horizontal option displays the graph with the root node at the left.
.*
.section Defining Graph View Legends
.*
.np
.ix 'graph view legends' 'in &br'
.ix 'inheritance legend menu item'
.ix 'call legend menu item'
.ix '&br' 'defining graph view legends'
The
.us Inheritance Legend
and
.us Call Legend
menu items in the
.us Options
menu allow you to change the &colour.s, line styles, and node styles
used in the graph views.
Changing the styles updates all open graph views in the current
session, as well as any new ones you open.
Saving the session configuration to an option file saves changes
made to the &colour.s and the lines and node styles.
.np
The
.us Inheritance Legend
and
.us Call Legend
dialogs are designed differently, but the
procedures for changing the graph styles are identical.
.np
To change the line and node styles for inheritance graphs, choose
.us Inheritance Legend
from the
.us Options
menu.
The
.us Inheritance Legend
dialog appears.
.np
To change the line and node styles for call graphs, choose
.us Call Legend
from the
.us Options
menu.
The
.us Call Legend
dialog appears.
.begstep
.step Click once on the line or node style
or use the up, down, right and left arrow keys to select
the line or node style you want to change.
.result
A box appears around the selected line.
.step Click on the Modify button.
.result
This opens the
.us Draw Style
dialog for the selected line or node style.
.step Click once on the desired line or node style
.orstep use the up and down arrow keys
to select the desired line or node style.
.result
The sample appearing in the
.us Example
field at the top of the dialog now reflects the currently selected
line or node style.
.step Click once on the desired &colour or use the up and down
arrow keys to select the desired &colour..
.result
The sample appearing in the
.us Example
field at the top of the dialog now reflects the currently selected
&colour..
.step Click on OK
to accept the new style and &colour setting.
.result
The
.us Draw Style
dialog closes, returning you to the
.us Inheritance Legend
or
.us Call Legend
dialog.
Select another line or node style to change and repeat this procedure.
.step Click on OK in the
.us Inheritance Legend
or
.us Call Legend
dialog when you have changed all desired &colour.s and styles for lines
and nodes.
.result
Clicking
.us OK
closes the dialog and updates all open inheritance or call graph
views with the selected &colour.s and line and node styles.
.endstep
.*
.section Selecting a Text Editor
.*
.np
.ix '&br' 'selecting a text editor'
.ix 'set text editor'
You can use your own favourite text editor from within the &br..
.begstep To select your own text editor:
.step Choose Set Text Editor
from the Options menu.
.result
The Set Text Editor dialog appears.
You can enter the name of the text editor in the first field.
You must also indicate whether the text editor is an executable
file or a Dynamic Link Library (DLL).
If the editor is an executable file (rather than a DLL), then you can
enter an argument line in the second field.
The argument line will be supplied to the editor whenever it is
started by the &br..
The argument line can include any of three different macros which will
be filled in by the &br..
The macros are:
.begnote
.note %f
The name of the file to be edited.
.note %r
The row in the file at which to position the cursor.
If the editor is invoked from a diagnostic message which contains a
line number then the row value is extracted from the message;
otherwise the row value is 1.
.note %c
The column in the file at which to position the cursor.
If the editor is invoked from a diagnostic message which contains a
column number then the column value is extracted from the message;
otherwise the column value is 1.
.endnote
.np
For example, if the editor argument line that you specified was:
.millust begin
file='%f' row='%r' col='%c'
.millust end
.pc
and you double click on an error message in the Log window that names
the file
.id foobar.c
with an error at line 215 and column 31, then the argument line
that is passed to your editor is:
.millust begin
file='foobar.c' row='215' col='31'
.millust end
.np
This flexibility allows you to specify the name of the file to edit
and the row and/or column at which to position the text cursor.
If no row or column is available, then the &br will supply the value
of 1 as a default.
.step Select OK
when you wish to confirm the selection of a new editor.
.orstep Select Cancel
when you wish to cancel the selection of a new editor.
.orstep Select Default
when you wish to restore the default editor selection
and then select OK or Cancel.
.endstep
.*
.section Automatically Saving Options on Exit
.*
.np
.ix '&br' 'saving options on exit'
.us Save Options on Exit
in the
.us Options
menu instructs the &br to automatically save the current options to an
options file.
To enable the automatic saving of options, select
.us Save Options on Exit
from the
.us Options
menu.
A check mark beside the menu item indicates that it is enabled.
To disable this option, select it again.
.np
See the section entitled :HDREF refid='brsave'. for more information
on saving options to a file.
.*
.endlevel
.*
.section Loading Options
.*
.np
.ix '&br' 'loading options'
.ix 'options' 'loading'
Use the
.us Load Options
menu to load an option file into your &br session.
.np
Choose
.us Load Options
from the
.us File menu.
The
.us Load Options File
dialog appears where you select the option file you want to load for
the current &br session.
.*
.section *refid=brsave Saving Options
.*
.np
.ix '&br' 'saving options'
There are three ways to save the current options to an option file:
.begbull $compact
.bull
Save Options
.bull
Save Options As
.bull
Save Options on Exit
.endbull
.np
An asterisk beside the option file name in the caption bar indicates
that changes were made to the options during the &br session and
should be saved.
This section describes each method for saving options to a file.
.begnote
.note Note:
If you have made option changes during the &br session and you choose
.us Exit
from the
.us File
menu without first saving the options, the &br prompts you to save the
options to a file.
Refer to the section entitled :HDREF refid='brquit'. for more
information.
.endstep
.begpoint $break
.point Save Options
Selecting
.us Save Options
from the
.us File
menu saves the updated options information to the current options
file.
To save options in this way, an options file must be specified in the
caption bar.
.ix '&br' 'save options'
.point Save Options As
.us Save Options As
in the
.us File
menu opens the
.us Save Options As
dialog.
Specify the filename of the option file to which you want to save the
current options.
Click on
.us OK
to close the dialog and save the options.
.point Save Options on Exit
.us Save Options on Exit
in the
.us Options
menu allows you to specify that the &br is to automatically save the
current options to an options file, if one exists.
When enabled, a check mark appears beside this menu item.
.np
When enabled and an option file exists, the &br saves the changes
without prompting when you close the session.
.np
When enabled and no option file exists, the &br displays a message box
prompting you to save the new options.
Choose
.ul
No
in this box to close the &br session without saving.
Choose
.ul
Yes
in this box to display a
.us Save As
dialog where you specify the option file to which you want to save the
new options.
.endpoint
.*
.section Setting Source Search Paths
.*
.np
.ix 'path option'
.ix '&br' 'path option'
.ix 'source search path'
.ix 'search path'
You can specify a command line option to the &br that allows you to
specify alternate source file search paths.
This option is useful when a database file is created on a system
different from the one that is used to browse the application source
code.
The syntax of the command line option is:
.millust begin
path path_spec1;path_spec2;...
.millust end
.np
Since the database files record explicit paths to source files, it is
likely that the path will no longer be valid once the software is
moved to another system.
.np
.ix 'path search'
When the &br cannot locate the specified file using its explicit path,
it will search the paths listed in the path option.