HP Visualize J5000 HP Workstations - Graphics Administration Guide For Red Hat - Page 22

Supported devices, Dynamic loading, Include inferiors fix

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

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 "/etc/X11/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. Note: Altering or removing files under /usr/X11R6/hp/lib/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 Graphics Administration Guide For Red Hat Linux 6.2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
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
"
/etc/X11/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.
_______________________________________________________________________
Note:
Altering or removing files under
/usr/X11R6/hp/lib/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
Graphics Administration Guide For Red Hat Linux 6.2