HP Visualize J5000 hp workstations - hp-ux 10.20 graphics administration guide - Page 33

Shared Memory Extension (MIT_SHM), MIT_SHM

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 33 highlights

to allow for synchronization with vertical retrace. To activate this optional X server mode, set the SwapBuffersOnVBlank Screen Option in the X*screens file before the X server is started Note: MBX_SWAP_BUFFERS_ON_VBLANK is obsolete with this release. The SwapBuffersOnVBlank Screen Option works for both DBE and MBX With this mode enabled, all MBX buffer swaps are synchronized with the monitor's vertical retrace period. This mode is not needed in drawables used for PEX rendering. PEX turns synchronization on and thus does not require this tuning. The MBX Application Programming Interface is thoroughly discussed in the PEXlib Programming Manual by Tom Gaskins, and published by O'Reilly & Associates, Inc. Consult that manual to understand the creation, manipulation, and destruction of MBX buffers. Since MBX is not an industry standard, and will be discontinued on HP-UX 11.0, developers should replace MBX calls with the appropriate DBE calls. Note: XmbufGetScreenInfo() can indicate that a window supports MBX even if only one MBX buffer is supported. An application should always check the max_buffers field in the returned XmbufBufferInfo structure before assuming that a window supports two MBX buffers Shared Memory Extension (MIT_SHM) The MIT shared memory extension provides both shared-memory XImages and shared-memory pixmaps based on the SYSV shared memory primitives. Shared memory XImages are essentially a version of the XImage interface where the actual image data is stored in a shared memory segment, and thus need not be moved through the Xlib interprocess communication channel. For large images, use of this facility can result in increased performance. Shared memory pixmaps are a similar concept implemented for the pixmap interface. Shared memory pixmaps are two-dimensional arrays of pixels in a format specified by the X server, where the pixmap data is stored in the shared memory segment. In all other respects, shared memory pixmaps behave the same as ordinary pixmaps and can be modified by the usual Xlib routines. In addition, it is possible to change the contents of these pixmaps directly without the use of Xlib routines merely by modifying the pixmap data. Page 33 Graphics Administration Guide for HP-UX 10.20

  • 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
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
to allow for synchronization with vertical retrace. To activate this optional X server mode, set the
SwapBuffersOnVBlank Screen Option in the X*screens file before the X server is started.
____________________________________________________________________________________
Note:
MBX_SWAP_BUFFERS_ON_VBLANK
is obsolete with this release. The SwapBuffersOnVBlank
Screen Option works for both DBE and MBX.
____________________________________________________________________________________
With this mode enabled, all MBX buffer swaps are synchronized with the monitor's vertical retrace
period.
This mode is not needed in drawables used for PEX rendering. PEX turns synchronization on and thus
does not require this tuning.
The MBX Application Programming Interface is thoroughly discussed in the PEXlib Programming
Manual by Tom Gaskins, and published by O'Reilly & Associates, Inc. Consult that manual to
understand the creation, manipulation, and destruction of MBX buffers.
Since MBX is not an industry standard, and will be discontinued on HP-UX 11.0, developers should
replace MBX calls with the appropriate DBE calls.
____________________________________________________________________________________
Note:
XmbufGetScreenInfo()
can indicate that a window supports MBX even if only one MBX buffer is
supported. An application should always check the max_buffers field in the returned
XmbufBufferInfo
structure before assuming that a window supports two MBX buffers.
____________________________________________________________________________________
Shared Memory Extension (
MIT_SHM
)
The MIT shared memory extension provides both shared-memory XImages and shared-memory
pixmaps based on the SYSV shared memory primitives.
Shared memory XImages are essentially a version of the XImage interface where the actual image data
is stored in a shared memory segment, and thus need not be moved through the Xlib interprocess
communication channel. For large images, use of this facility can result in increased performance.
Shared memory pixmaps are a similar concept implemented for the pixmap interface. Shared memory
pixmaps are two-dimensional arrays of pixels in a format specified by the X server, where the pixmap
data is stored in the shared memory segment. In all other respects, shared memory pixmaps behave the
same as ordinary pixmaps and can be modified by the usual Xlib routines. In addition, it is possible to
change the contents of these pixmaps directly without the use of Xlib routines merely by modifying the
pixmap data.
Graphics Administration Guide for HP-UX 10.20
Page 33