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

Save as Screen Default, Remove Screen Default, hp CDE and hp VUE, Shared Memory Usage

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

If the colormap used by the selected window is also used by other windows, their appearance will change along with the actual window you selected. If the only colormap used by the selected window is the default colormap, then you will need to check the "Modify Default Colormap" box as well. Modifying the default colormap will change the appearance of many windows and user-interface elements. Save as Screen Default When you select the "Save as Screen Default" button, the current gamma value will be saved in the appropriate X screens file (X0screens for screen 0, X1screens for screen 1, etc.). When you quit CDE and X windows, the value you save in the X screens file will be used the next time X is started. Since the X screens file is a system resource, your system administrator determines who has permission to modify that file. Remove Screen Default If you select the "Remove Screen Default" button, the default gamma value saved in the X screens file will be removed and the gamma value for all windows will be reset to 1.0. This option also requires appropriate permissions to modify the X screens file. hp CDE and hp VUE Hewlett-Packard is in the process of a transition to a standard user environment. Two user environments were shipped with hp-UX 10.20: hp VUE and hp CDE (Common Desktop Environment). As of hp-UX 10.20, hp CDE is the default user environment, and although hp VUE is still available with hp-UX 10.20, it is not the default. See the Common Desktop Environment User's Guide for more information on hp CDE. From a 3D graphics point of view, the change in user environments should have no effect. Shared Memory Usage Graphics processes use shared memory to access data pertaining to the display device and the X11 resources created by the server (for example, color maps, cursors, etc.). The X11 server initiates an independent process called the Graphics Resource Manager (GRM) to manage these resources among graphics processes. One problem encountered with GRM shared memory is that it may not be large enough to run some applications. hp PEX, Starbase, and hp-PHIGS use GRM shared memory for VM double-buffering. If your application is running on a low-end graphics system (for example, an hp 710 or 712), you set the environment variable hp_VM_DOUBLE_BUFFER (or SB_710_VM_DB), and you have several large double-buffered windows open simultaneously, then your application could use up available GRM shared memory. If you encounter a dbuffer_switch error message while using VM double-buffering, you may have encountered this problem. Page 124 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
If the colormap used by the selected window is also used by other windows, their appearance will
change along with the actual window you selected.
If the only colormap used by the selected window is the default colormap, then you will need to check
the "Modify Default Colormap" box as well. Modifying the default colormap will change the appearance
of many windows and user-interface elements.
Save as Screen Default
When you select the "Save as Screen Default" button, the current gamma value will be saved in the
appropriate X screens file (X0screens for screen 0, X1screens for screen 1, etc.). When you quit CDE
and X windows, the value you save in the X screens file will be used the next time X is started.
Since the X screens file is a system resource, your system administrator determines who has permission
to modify that file.
Remove Screen Default
If you select the "Remove Screen Default" button, the default gamma value saved in the X screens file
will be removed and the gamma value for all windows will be reset to 1.0.
This option also requires appropriate permissions to modify the X screens file.
hp CDE and hp VUE
Hewlett-Packard is in the process of a transition to a standard user environment. Two user environments
were shipped with hp-UX 10.20: hp VUE and hp CDE (Common Desktop Environment). As of hp-UX
10.20, hp CDE is the default user environment, and although hp VUE is still available with hp-UX
10.20, it is not the default. See the Common Desktop Environment User's Guide for more information
on hp CDE.
From a 3D graphics point of view, the change in user environments should have no effect.
Shared Memory Usage
Graphics processes use shared memory to access data pertaining to the display device and the X11
resources created by the server (for example, color maps, cursors, etc.). The X11 server initiates an
independent process called the Graphics Resource Manager (GRM) to manage these resources among
graphics processes. One problem encountered with GRM shared memory is that it may not be large
enough to run some applications.
hp PEX, Starbase, and hp-PHIGS use GRM shared memory for VM double-buffering. If your
application is running on a low-end graphics system (for example, an hp 710 or 712), you set the
environment variable
hp_VM_DOUBLE_BUFFER
(or
SB_710_VM_DB
), and you have several large
double-buffered windows open simultaneously, then your application could use up available GRM
shared memory. If you encounter a dbuffer_switch error message while using VM double-buffering, you
may have encountered this problem.
Graphics Administration Guide for HP-UX 10.20
Page 124