Table of Contents
Previous Chapter
Figure 486 : The Preference Manager Window.
-----
(fig)
-----
The items that build up the Preferences window will now be discussed in detail:
Figure 487 : Node in the Tree Area.
-----
(fig)
-----
Example 34 : A Line in the Preferences WindowGiven the following line in the Preferences window, with all View Options turned "on":
Figure 488 : A Line in the Preferences Window.
-----
(fig)
-----
The information on the line in Figure 488 should be interpreted as:
---------------------------------------------------------------
Item Interpretation
---------------------------------------------------------------
(fig) The icon informing that the preference
parameter is a boolean parameter (0/1,
false/true or off/on parameter.
Editor*SymbolMenu The name of the preference parameter,
consisting of
· the name of the tool it affects,
Editor
· the name of the parameter,
SymbolMenu
Separated with an asterisk
off The current value for the parameter.
(off) The saved value for the parameter.
((on)) The default value for the parameter.
[User] The parameter's source, in this case the
parameter is defined by the user.
Show the symbol menu The parameter's description, i.e. what
tool property the parameter affects.
---------------------------------------------------------------
The tree is a visualization of the merged preference parameters, supplied from different sources (see "Search order when Reading Preference Parameters" on page 1501), as the SDT tools will perceive them. Furthermore, each node in the tree can be collapsed or expanded (see "Collapse" on page 1492) in order to reduce or extend the amount of information that is visible, thus facilitating the work with the tool. It is also possible to filter the information that is displayed with respect to various View Options (see page 1493).
Figure 489 : Nodes Marked as Dirty.
-----
(fig)
-----
There are six types of preference parameters:
-------------------------------------------------------------- Icon Edit Area -------------------------------------------------------------- (fig) (fig) Textual Preference
Some of the menu-choices available beneath the pull-down menus are also available in Popup Menu and / or Quick Buttons.
Figure 490 : The File Menu
-----
(fig)
-----
The items on this menu are:
But, before saving the preference settings, SDT will warn the user if he has modified preferences that are defined as company or project preferences:
Figure 491 : Attempting to Save a Modified Project or Organization Parameter
-----
(fig)
-----
------------------------------------------------------------------ Caution! Clicking this button should be done after having considered the im plications. ------------------------------------------------------------------
Figure 492 : The Confirm to Revert Dialog.
-----
(fig)
-----
Figure 493 : The Print Dialog.
-----
(fig)
-----
See also "Document" on page 1448 and "Destination" on page 1452 for a description of the various print options that are supported.
Figure 494 : Information about Preference Sources.
-----
(fig)
-----
The message shows three items:
If there are any parameter values that are modified but not saved, the tool prompts to save the changes.
Figure 495 : The Save Preferences at Exit Dialog.
-----
(fig)
-----
Figure 496 : The Edit Menu
-----
(fig)
-----
The available menu-choices are:
A dialog is displayed following invocation of the command:
Figure 497 : The Unsave Dialog.
-----
(fig)
-----
Figure 498 : The File Menu
-----
(fig)
-----
The menu choices available beneath the View menu are:
The operation is also available on the Popup Menu and with a double-click.
The operation is also available on the Popup Menu.
The operation is also available on the Popup Menu and with a double-click.
The operation is also available on the Popup Menu
Figure 499 : The View Options Dialog.
-----
(fig)
-----
The dialog contains the following toggle buttons:
The tool bar is visible by default.
The status bar is by default visible.
--------------------------------------------------------------------- Note: The name of a preference parameter consists of a combination of a tool name and of the parameter itself (see "Syntax of Preference Files" on page 1500). The filter option compares the text strings without respect to upper or lower case characters. ---------------------------------------------------------------------By default, no filtering is applied.
Tool names are not displayed by default.
Saved values are displayed within one level of parentheses (saved value). See Example 34 on page 1482.
Saved values are displayed by default.
Default values are displayed within two levels of parentheses ((default value)). See Example 34 on page 1482.
Default values are not displayed by default.
Parameter descriptions are not displayed by default.
The scale is set using a modal dialog:
Figure 500 : The Set Scale Dialog.
-----
(fig)
-----
Figure 501 : The Tools Menu.
-----
(fig)
-----
---------------------------- Collapse All See page 1492. Expand All See page 1492. ----------------------------
------------------------ Collapse See page 1492. Expand See page 1492. ------------------------
-----------------------------------------------------------
Set Saved Value See page 1490.
Set Default Value See page 1490.
Help Request on-line help for the preference
parameter in question.
-----------------------------------------------------------
-------------------------------------------------------
Accelerator Operation
-------------------------------------------------------
Arrow Up Move selection up among the expanded nodes
Arrow Down Move selection down among the expanded
nodes
Page Up Scroll up
Page Down Scroll down
Home Scroll left
End Scroll right
Ctrl-Home Display first line
Ctrl-End Display last line
Space or Expand or Collapse node (see page 1492)
Return Traverse through option menu.
Toggle parameters on/off.
F2 Raise the Popup Menu
-------------------------------------------------------
The Preference Tool manages these files and provides the graphical user support for customizing SDT in an easy way.
The following items constitute the various sources for preference parameters. The source identifier may be made visible with the Value Sources options in the View Options dialog.
-----------------------------------------------------------------
Source Identifier Source Description
-----------------------------------------------------------------
[User] The user's preference file
[User (No Save)] The user's preference file, will be removed
from the user's preference file next time the
parameters are saved
[Project] The project preference file
[Company] The company preference file
[Default] The default factory settings.
-----------------------------------------------------------------
The user's preference file is identified by:
$HOME/.sdtpref------------------------------------------------------------- Note: $HOME $HOME is assumed always to be defined in an UNIX environment. -------------------------------------------------------------
The project preference file is identified by:
$SDTPREF/.sdtpref---------------------------------------------------------------------- Note: $SDTPREF $SDTPREF, if not set, will simply disable the project preference file feature. ----------------------------------------------------------------------
The company preference file is identified by:
$sdtrelease/.sdtpref-------------------------------------------------------------- Note: $sdtrelease $sdtrelease is assumed always to be set in an SDT environment. --------------------------------------------------------------
tool*parameter: value Example 35 : A Line in Preferences FileAn example line in a preferences file could look like this:
Print*Scale:100Meaning that the scale when printing is 100%.
The order of appearance of the parameters in a file is of no significance.
When an SDT tool starts, it will automatically (i.e. no user-interaction is required) retrieve the preference values in an incremental way, following the order of search described below and illustrated in Figure 502:
Figure 502 : How SDT Searches for Preference Parameters.
-----
(fig)
-----
The above implies modifying a parameter that was originally defined as a project or organization parameter, it will be from now on be considered as an user-defined parameter. The user is however be notified about this (see Figure 491 on page 1487).
Table of Contents
Next Chapter