Filter
Top Products
Dynamic Loading
HP's X server now dynamically loads the appropriate device drivers and extensions based on the target
graphics display device and the extensions the device driver supports. This feature should be transparent
to X server users.
When possible, the loading of X extensions is deferred until the first protocol request is encountered for
a given extension. This feature should be transparent to X server users; however, it is expected to
provide some performance enhancement.
Dynamically loaded modules are recorded by the X server in the files "/var/X11/Xserver/logs/X*.log",
where the "*" of X*.log reflects the display identifier for that given run. Only that last invocation against
a given display identifier is retained. The log file contains the parsed contents of the given X*screens
file and the full path name for all dynamically loaded modules for the given X server invocation.
Deferred loaded modules are recorded as they are referenced.
____________________________________________________________________________________
Caution: Altering or removing files under /usr/lib/X11/Xserver may prevent the X server from running.
____________________________________________________________________________________
Include Inferiors Fix
When a client application creates an X Graphics Context (GC), it is possible to specify the
subWindowMode component. The two possible values are ClipByChildren (default) and
IncludeInferiors. If the GC specifies ClipByChildren, any rendering to a window with inferior windows
(i.e., the child is wholly enclosed by the parent) will appear only in the destination window. In other
words, the rendering will not take place inside the inferiors. If the GC specifies IncludeInferiors, and the
same rendering request is made, it is the responsibility of the X Server to ensure that the rendering is not
clipped from the inferior windows. In other words, the rendering will appear in the destination window
and the inferior windows.
With the advent of multi-layer devices, the IncludeInferiors mode became defective. Depending upon
which layer or hardware buffer the destination drawable and inferior windows were in, the rendering
may or may not have taken place. Also, the GetImage protocol clearly specifies that the default
GetImage behavior is to include the depth-dependant contents of inferior windows (in other words,
GetImage requires that IncludeInferiors work properly).
As of the 10.10 release, HP has offered a solution to the IncludeInferiors defect. Some customers create
their test image archives using XGetImage (which currently returns incorrect data for multi-layer and
double-buffered devices). Therefore, the Include Inferiors Fix will not be enabled by default. To enable
the Include Inferiors Fix, add the EnableIncludeInferiorsFix Screen Option to the X*screens file.
Graphics Administration Guide for HP-UX 10.20
Page 39