Table of Contents
Advertisement
Chapter 11: X Resources and the Graphical Interface
You can create your own scheme files, if you choose
The debugger's graphical interface supports user-defined scheme files. The
interface searches two places for user-defined scheme files and loads any it
finds after loading the system scheme files. Refer to any of the scheme files
mentioned for information about where to place your own scheme files.
Scheme files continue the load sequence for X resources
Scheme files extend the load order for finding X resources. System scheme file
resources override all other resources gathered so far, and user-defined
scheme files, in turn, override the system scheme files. Continuing from the
load order list previously, the scheme files follow, in the order
6
7
8
Please note the dot (.) in the ".HP64_schemes" directory name.
You can force the debugger's graphical interface to use
certain schemes
Five application-specific resources allow you to force the interface to use
certain schemes. The resources and what they control are as follows:
HP64_Debug.platformScheme:
340
/usr/hp64000/lib/X11/HP64_schemes/Debug.Label
/usr/hp64000/lib/X11/HP64_schemes/< platform> /Debug.< scheme>
$XAPPLRESDIR/HP64_schemes/Debug.Label
$XAPPLRESDIR/HP64_schemes/< platform> /Debug.< scheme>
Just as $XAPPLRESDIR can point to a system-wide app-defaults file, so
can it point to a set of system-wide scheme files.
$HOME/.HP64_schemes/Debug.Label
$HOME/.HP64_schemes/< platform> /Debug.< scheme>
Controls the platform scheme chosen by the interface. This resource is
particularly useful in mixed-platform environments where you might be
executing the interface remotely on an HP 9000 computer, but displaying
the interface on a Sun SPARCsystem computer. In this situation, you may
wish to set the resource to use the SunOS scheme so that you can use the
same key and mouse button bindings as other Sun OpenWindows
applications.
Advertisement
Table of Contents
