| Are you using Motif Window Manager w/ Overlays ? If so, there is a
corresponding UG file to enable overlays (ugii_dir:UGII_ENV.DAT).
Here's the section on overlays:
# The UGII_USE_OVERLAYS flag controls whether overlays are used. If
# undefined, overlays are used by default on all graphics boards that
# support them. Use of overlays enables the UI dialogues to reside in
# overlay planes, so that if the UI dialog covers the graphics window,
# no damage is made to the graphics window. Thus no refresh is needed
# to repair the graphics window, which improves performance.
# To disable overlays, set UGII_USE_OVERLAYS=0
UGII_USE_OVERLAYS=1
Also, make sure the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file has
the correct entries in it to disable backing store, and to address the
required values for the decw$server* parameters.
e.g. (for ZLX-M1)
$ ! Start UGII parameters - added 16-JAN-1997 10:04:13.92
$ define /nolog decw$server_file_limit 400
$ define /nolog decw$server_enqueue_limit 2000
$ define /nolog decw$server_wsdef 10240
$ define /nolog decw$server_wsquota 20480
$ define /nolog decw$server_wsextent 32768
$ define /nolog decw$server_page_file 270000
$ decw$server_disable_backing_store :== t
You can use the DECW$UTILS:DECW$DEFINE_UTILS.COM to enable X window
utilities like "xwininfo" and "xdpyinfo" to obtain the current state of
your windowing/graphics env.
Hope this helps...
-Bill
P.s.
The following info is from the Open3D 3.5 Release Notes, and addresses
some of the problems described in 491.0:
2.4.6 Motif Window Manager Overlay Problem on ZLX-M and ZLX-L
If you use the Motif Window Manager (mwm) in overlay mode with a
pseudocolor main window and an overlapping pseudocolor overlay,
the intersection may show a black rectangle when the applica-
tions have exited. This condition is a visual error only and
has no effect on programs running before or after the error.
Overlay windows and regular windows are in different layers,
so drawing in an overlay window will not disturb the pixels of
the regular window, and vice versa. If you draw an invisible
pixel into an overlay window, the pixel of the nonoverlay
window beneath that window will show through.
3.7.2 Window Manager for Overlays
Version 3.5 supplies an optional window manager called
DECW$MWM_OVERLAY.EXE in SYS$SYSTEM:. This window manager will take ad-
vantage of the extra planes of memory available on many of the
graphics accelerators.
To make this window manager the default for a specific user:
1. Log in to your workstation.
2. Select the Options Menu from the Session Manager.
3. Click on the Automatic Startup Item.
4. In the Session Manager: Automatic Startup Dialog box,
select the Window Manager item from the righthand list.
5. Remove the Window Manager Item by clicking on the button
with the left pointing arrow. This button is in the center of
the dialog box.
6. Add the new window manager to the automatic startup list.
This is done by scrolling down the list until you find the
item marked "Window MGR with Overlays" and clicking on
that item. You should now see the new item appear in the
righthand list.
7. To save these changes, click on the "OK" button. Then
select "Save Session Manager" from the Options Menu.
8. These changes will take effect the next time you log into
your workstation.
The new window manager will put all the window borders and
banners in the overlay planes. If you currently have an application
that was written to use overlays without this window manager,
you will need to modify the application to avoid colormap
problems. The best way to do this is to share the overlay
colormap with the window manager. This can be done by querying the
server property name SERVER_OVERLAY_COLORMAPS. This property will
return the 32-bit value that is the overlay colormap ID.
It is strongly suggested that you share colormaps with the
window manager, as the hardware supports only one colormap
for the overlay planes. If you create and install your own
colormap, then you will have colormaps flashing on the screen and will
change the colors of the window manager's borders and banners.
3.8 Multiple Colormaps
The following discussion of multiple color maps applies to
all supported graphics options except the ZLX-E1, the ZLXp-E1,
the PowerStorm 3D10 and the PowerStorm 3D30. Options with
multiple colormaps support multiple, simultaneously-installed
colormaps.
Applications should not install or deinstall colormaps them-
selves. The window manager should perform these actions. How-
ever, the application is responsible for providing the window
manager with hints as to which colormaps to install or dein-
stall. You provide this information using the Xlib function
XSetWMColormapWindows(). This function sets the WM_COLORMAP_
WINDOWS property for a given window.
For information on how to use this function and how the window
manager interprets the property, see The X Window System by
Scheifler and Gettys, 3rd Edition (Section 14.1.11, Setting and
Reading the WM_COLORMAP_WINDOWS Property, pages 425-426, and
Section 4.1.8, Colormaps, page 649-651).
Applications written and debugged on systems with only one colormap
may appear incorrect on a system with multiple colormaps.
There are several application errors that can cause this, but
the most prevalent is not having the correct colormap associated
with all the windows that require it. To correct this
problem, use XChangeWindowAttributes to set the colormap for all
windows in the application that require the colormap.
|