![HP 68000 Series User Manual Download Page 272](http://html.mh-extra.com/html/hp/68000-series/68000-series_user-manual_157001272.webp)
Instead of specifying the foreground color for the tracker quit button by using
a resource name made up of instance names as in the last example, you could
instead use a class name, as follows:
tracker.panel.control.XmPushbutton.foreground: white
Using class names in this way makes it easier to specify resources because it
relieves you from having to discover the names of particular widgets in an
application. A long string of instance names or class names is still a long
string of names, however. Fortunately, a wildcard helps to make the shortcut a
true shortcut. The wildcard is an asterisk ("*"). It can be used to replace any
number of class or instance names in a resource name. The last example could
now be shortened to either of the following:
tracker*XmPushButton.foreground: white
tracker*quit.foreground: white
But wait, there is trouble ahead
An X Window System application maintains a complete list of resources, and
the application knows the complete instance and class names for each
resource. Because you can specify resource values using shortened notation,
the application, when starting up, must match specified values to individual
resources. Some general rules apply:
•
Either a class name or instance name from the request must match each
class or instance name in the application’s list of resources.
•
Entries prefixed by a dot are more specific and therefore have precedence
over entries prefixed by an asterisk.
•
Instance names are more specific and therefore have precedence over class
names.
•
Matching is done from left to right. Instance or class names appearing at
the beginning of the specification have precedence over those later in the
specification.
As you can quickly see, resource matching favors specific resource names over
general resource names. General resource names, especially those involving
class names, can have unexpected and unintended effects. Consider the last
example again. The resource specification
Chapter 8: X Resources and the Graphical Interface
250
Summary of Contents for 68000 Series
Page 1: ...User s Guide HP B1466 68000 Series Debugger Simulator ...
Page 22: ...Contents xxii ...
Page 23: ...Part 1 Quick Start Guide ...
Page 24: ...Part 1 2 ...
Page 57: ...Part 2 User s Guide ...
Page 58: ...Part 2 36 ...
Page 140: ...Chapter 3 Loading and Executing Programs Using the Debugger with the Branch Validator 118 ...
Page 234: ...Chapter 6 Using Macros and Command Files Using Command Files 212 ...
Page 266: ...Chapter 7 Configuring the Debugger Setting X Resources 244 ...
Page 267: ...Part 3 Concept Guide ...
Page 268: ...Part 3 246 ...
Page 269: ...8 X Resources and the Graphical Interface An introduction to X resources 247 ...
Page 281: ...Part 4 Reference ...
Page 282: ...Part 4 260 ...
Page 283: ...9 Debugger Commands Detailed descriptions of command line commands 261 ...
Page 436: ...Chapter 9 Debugger Commands Window Toggle_View 414 ...
Page 466: ...Chapter 10 Expressions and Symbols in Debugger Commands Symbolic Referencing 444 ...
Page 467: ...11 Predefined Macros 445 ...
Page 504: ...Chapter 11 Predefined Macros write 482 ...
Page 505: ...12 Debugger Error Messages A list of the error messages generated by the debugger 483 ...
Page 524: ...Chapter 12 Debugger Error Messages 502 ...
Page 531: ...Part 5 Installation Guide ...
Page 532: ...Part 5 510 ...
Page 533: ...14 Installation How to install the debugger software on your computer 511 ...
Page 584: ...Index 562 ...