How X Resource Specifications Are Loaded - HP 64746 User Manual

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:
1 Apply to ALL HP64_Softkey applications:
HP64_Softkey*<resource>: <value>
2 Apply to specific types of HP64_Softkey applications:
emul*<resource>: <value> (for the emulator)
perf*<resource>: <value> (for the performance analyzer)
3 Apply to all HP64_Softkey applications, but only when they are connected to a
particular type of microprocessor:
*m68302*<resource>: <value> (for the 68302)
*m68020*<resource>: <value> (for the 68020)
4 Apply to a specific HP64_Softkey application connected to a specific
processor:
perf.m68302*<resource>: <value> (for the 68302 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 68302 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.
X Resources and the Graphical User Interface
Chapter 15: Concepts
541