Table of Contents
Advertisement
Specific Names Override General Names
A more specific resource specification will override a more general one when
both apply to a particular widget or application.
The names for the application and the main window widget in HP64_Softkey
applications have been chosen so that you may specify custom resource
values that apply in particular situations:
Apply to ALL HP64_Softkey applications:
HP64_Softkey*<resource>: <value>
Apply to specific types of HP64_Softkey applications:
emul*<resource>: <value> (for the emulator)
perf*<resource>: <value> (for the performance analyzer)
Apply to all HP64_Softkey applications, but only when they are
connected to a particular type of microprocessor:
*m6833x*<resource>: <value> (for the 6833x)
*m68020*<resource>: <value> (for the 68020)
Apply to a specific HP64_Softkey application connected to a specific
processor:
perf.m6833x*<resource>: <value> (for the 6833x perf. analyzer)
emul.m68020*<resource>: <value> (for the 68020 emulator)
If all four examples above are used for a particular resource, #3 will override
#2 for all applications connected to a 6833x emulator, and #4 will override #2,
but only for the specifically mentioned type of microprocessor.
When modifying resources, your resource paths must either match, or be
more specific than, those found in the application defaults file.
How X Resource Specifications are Loaded
When the Graphical User Interface starts up, it loads resource specifications
from a set of configuration files located in system directories as well as
user-specific locations.
Concepts
495
Advertisement
Table of Contents
