VMS Workstation Software
Release Notes
Version 4.1
Order Number: AA-KP45D-TE
March 1989
This document provides supplemental information about
Version 4.1 of VMS Workstation graphics software. It
describes all the changes for Version 4.1 and lists
problems and restrictions.
Software Version: VAX/VMS Version 5.0 and
later
Revision/Update Information: This manual replaces the
VMS Workstation Release
Notes, Version 4.0 and
VMS Workstation Release
Notes, Version 3.3. This
is for VWS Field Test
Version 4.1.
Digital Equipment Corporation
________________________
March 1989
__________
The information in this document is subject to change
without notice and should not be construed as a
commitment by Digital Equipment Corporation. Digital
Equipment Corporation assumes no responsibility for
any errors that may appear in this document.
The software described in this document is furnished
under a license and may be used or copied only in
accordance with the terms of such license.
No responsibility is assumed for the use or
reliability of software on equipment that is not
supplied by Digital Equipment Corporation or its
affiliated companies.
__________
Copyright ©1989 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
__________
The postpaid READER'S COMMENTS form on the
last page of this document requests the user's
critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment
Corporation:
DEC DIBOL UNIBUS
DEC/CMS EduSystem VAX
DEC/MMS IAS VAXcluster
DECnet MASSBUS VMS
DECsystem-10 PDP VT
DECSYSTEM-20 PDT
DECUS RSTS
DECwriter RSX DIGITAL
This document was prepared using VAX DOCUMENT, Version
1.1
_______________________________________________________
Contents
_________________________________________________
PREFACE ix
_______________________________________________________
CHAPTER 1 VMS WORKSTATION SOFTWARE SUMMARY OF
NEW AND CHANGED FEATURES 1-1
_________________________________________________
1.1 VMS WORKSTATION SOFTWARE VERSION
4.1 1-1
1.1.1 Prerequisite Software _________ 1-1
1.1.2 Licensing _____________________ 1-1
1.1.3 Hardcopy UIS-HCUIS ____________ 1-2
_________________________________________________
1.2 NEW FEATURES FOR VWS VERSION 4.1 1-2
1.2.1 Tektronix 4125 Emulator _______ 1-2
1.2.2 Loading Fonts _________________ 1-3
1.2.3 ReGIS Plane Mask Support ______ 1-3
1.2.4 New UIS Routines for VWS
Version 4.1 ___________________ 1-4
1.2.5 VT200 Terminal Emulator Color
Map Changes ___________________ 1-4
1.2.5.1 Changes to UISBG.DAT for Color
Terminals, 1-5
1.2.5.2 Changes to UIS$CREATE_TERMINAL for
Color Terminals., 1-5
1.2.6 Multilevel Device Interrupt
Dispatching for Q22 Bus
Devices _______________________ 1-7
1.2.6.1 Ensuring That the Q22 Bus Is
Properly Configured, 1-8
iii
Contents
_________________________________________________
1.3 CHANGED FEATURES FOR VMS
WORKSTATION SOFTWARE VERSION 4.1 1-9
1.3.1 New Hardware Support __________ 1-10
1.3.2 132-Column Terminal Fonts _____ 1-10
1.3.3 Debugger ______________________ 1-10
1.3.4 Printer Setup Options _________ 1-10
1.3.5 SYS$FONT Logical Name _________ 1-11
_______________________________________________________
CHAPTER 2 VMS WORKSTATION SOFTWARE RESOLVED
PROBLEMS 2-1
_________________________________________________
2.1 VMS WORKSTATION SOFTWARE VERSION
4.1 RESOLVED PROBLEMS 2-1
2.1.1 UIS and UISDC Routines ________ 2-1
2.1.1.1 UIS$GET_LINE_WIDTH, 2-1
2.1.1.2 UIS$GET_OBJECT_ATTRIBUTES, 2-1
2.1.1.3 UIS$SET_POINTER_PATTERN and
UISDC$SET_POINTER_PATTERN, 2-1
2.1.1.4 UIS$SET_TB_AST, 2-2
2.1.1.5 UISDC$EXECUTE_DOP_SYNCH, 2-2
2.1.2 User Interface ________________ 2-2
2.1.3 Invalid Position Pointer
Value _________________________ 2-2
2.1.4 Italian Keyboard ______________ 2-3
2.1.5 Shrink to Icon Operation
Resulting in Process Hang _____ 2-3
2.1.6 Render Operation ______________ 2-3
2.1.6.1 During DEBUG Startup, 2-3
2.1.7 UIS$PRINT_DESTINATION _________ 2-3
2.1.8 UISENTRY.H ____________________ 2-4
2.1.9 Late Delivery of ASTs _________ 2-4
iv
Contents
2.1.10 SYSTEM PASSWORD _______________ 2-4
_______________________________________________________
CHAPTER 3 VMS WORKSTATION SOFTWARE PROBLEMS
AND RESTRICTIONS 3-1
_________________________________________________
3.1 VWS STARTUP PROCEDURE IN NEW
LOCATION 3-1
_________________________________________________
3.2 AUTOGEN PROBLEM 3-1
_________________________________________________
3.3 MOUSE INOPERATIVE ON FAST
PROCESSORS 3-2
_________________________________________________
3.4 REGIS RESTRICTIONS 3-2
_________________________________________________
3.5 FONTS LOADED BY DEFAULT AND SLOW
PAINTING OF POPPED WINDOWS 3-2
_________________________________________________
3.6 PRINT DESTINATION RESTRICTION 3-3
_________________________________________________
3.7 COLOR VAXSTATIONS IN A CLUSTER
ENVIRONMENT 3-4
_________________________________________________
3.8 SET HOST/DTE 3-4
_________________________________________________
3.9 SETTING OF TTY_CLASSNAME SYSGEN
PARAMETER 3-4
v
Contents
_________________________________________________
3.10 SETTING OF MULTIPROCESSING SYSGEN
PARAMETER 3-4
_________________________________________________
3.11 USER INTERFACE 3-4
3.11.1 VAXstation II/GPX Boot
Problem _______________________ 3-5
3.11.2 Restriction with Autologin ____ 3-5
_________________________________________________
3.12 PROGRAMMING INTERFACE 3-5
3.12.1 UIS$C_TEXT_WRITE-16-Bit Text
Problem _______________________ 3-5
3.12.2 UIS$CIRCLE and
UIS$ELLIPSE-Overflow
Problem _______________________ 3-6
3.12.3 UIS$DISABLE_KB and
UIS$DISABLE_VIEWPORT_KB-AST Not
Delivered _____________________ 3-6
3.12.4 UIS$EXTRACT_OBJECT-Incorrect
Length Returned _______________ 3-6
3.12.5 UIS$HSV_TO_RGB-Saturation
Parameter = 0.0 _______________ 3-7
3.12.6 UIS$SET_KB_ATTRIBUTES-Spurious
Data __________________________ 3-7
3.12.7 UIS$SET_POINTER_AST-Late
Execution of Exit AST
Routines ______________________ 3-7
3.12.8 Drawing Images That Use Eight
Bits/Pixel ____________________ 3-8
_________________________________________________
3.13 TEXT PROBLEMS 3-8
3.13.1 Extracting Transformed Control
Lists _________________________ 3-8
vi
Contents
3.13.2 Tabs in Control Lists _________ 3-9
3.13.3 Text Placement and Display
Lists _________________________ 3-9
3.13.4 Text Formatting Problems ______ 3-9
3.13.5 Sloped Text ___________________ 3-10
3.13.6 Restrictions on Writing Modes
That Change the Background ____ 3-11
_________________________________________________
3.14 DEVICE DRIVER INTERFACE 3-12
3.14.1 MOVE/ROTATE DOP-Specifying
Scaling _______________________ 3-12
3.14.2 Using DOPs with
UISDC$SET_CLIP ________________ 3-13
_________________________________________________
3.15 SYSTEM MANAGEMENT INTERFACE 3-13
_________________________________________________
3.16 USER INTERFACE 3-13
_________________________________________________
3.17 PROGRAMMING INTERFACE 3-14
3.17.1 Specifying a Negative Value As
Start_deg or End_deg Causes
Incorrect Drawing of a Circle
or Ellipse ____________________ 3-16
_______________________________________________________
APPENDIX A DESCRIPTION OF NEW ROUTINES A-1
_________________________________________________
A.1 NEW VWS VERSION 4.1 UIS ROUTINES A-1
UIS$GET_PLANE_MASK A-2
UIS$SET_PLANE_MASK A-4
vii
Contents
_______________________________________________________
INDEX
viii
_______________________________________________________
Preface
This document provides supplemental information about
the Version 4.1 VMS Workstation Software. It also
describes all changes to the software since Version
4.0. If you have not already done so, please read
the Read Me First information included with your
documentation.
__________________________________________________________________
Intended Audience
This manual is for graphic programmers and users
who should know about new features, problems and
restrictions, and changes to existing documentation.
All users should read this document before using the
VMS Workstation graphics software.
__________________________________________________________________
Document Structure
The VMS Workstation Release Notes, Version 4.1, is
arranged in three chapters and two appendixes that
cover the following topics:
o Chapter 1-Summary of new and changed features
o Chapter 2-Resolved problems
o Chapter 3-Problems and restrictions
o Appendix A-Descriptions of added features
o Appendix B-New routine descriptions
ix
Preface
__________________________________________________________________
Associated Documents
The following manuals are related to this document:
o VMS Workstation Software Installation Guide
o VMS Workstation User's Guide
o VMS Workstation Graphics Programming Guide
o VMS Workstation Video Device Driver Manual
o VMS Workstation Guide to Printing Graphics
o VMS Workstation Software SIGHT Installation and
User's Guide
o Using the VMS Workstation Software Tektronix 4125
Emulator
__________________________________________________________________
Conventions
Unless otherwise noted, the following conventions are
used in this manual in displaying examples and the
requirements of user input to the system.
_______________________________________________________
Convention______________Meaning________________________
<RETURN> This symbol indicates that you
press the key marked <RETURN>.
<CTRL/x> This symbol indicates that
you must press the key
labeled <CTRL> while you
simultaneously press another
key, for example, <CTRL/C>,
<CTRL/Y>, <CTRL/O>.
x
Preface
_______________________________________________________
Convention______________Meaning________________________
Ellipsis Vertical series of periods, or
ellipsis, mean either that not
. all the data that the system
. would display in response
. to the particular command is
shown or that not all the data
a user would enter is shown.
file-spec, . . . Horizontal ellipsis indicates
that additional parameters,
values, or information can be
entered.
[Square brackets] Square brackets indicate that
the enclosed item is optional.
(Square brackets are not,
however, optional in the
syntax of a directory name
in a file specification or
in the syntax of a substring
specification in an assignment
statement.)
Quotation marks The term quotation marks
is used to refer to double
quotation marks ("). The term
apostrophe is used to refer to
a single quotation mark (').
Italics Italicized words indicate that
________________________you_should_supply_a_value._____
xi
_______________________________________________________
1 VMS Workstation Software Summary of New and Changed
Features
This chapter describes major changes and added
features in VMS Workstation Software since Version
4.0.
__________________________________________________________________
1.1 VMS Workstation Software Version 4.1
___________________________
1.1.1 Prerequisite Software
You must have VMS Version 5.0 or later installed
to run VMS Workstation Software Version 4.1. Older
versions of VMS Workstation Software do not run on VMS
Version 5.0, nor does VMS Workstation Software Version
4.1 run on older versions of VMS.
___________________________
1.1.2 Licensing
VMS Workstation Software Version 4.1 uses the VMS
License Management Facility (LMF). To run VWS on a
particular node, you must have a valid VWS license
loaded. If the license is not properly loaded before
you invoke the VWS startup procedure, an error message
appears on the console and VWS terminates. If this
occurs, load the VWS license and re-invoke the VWS
startup procedure.
Refer to the VMS LMF documentation for more
information on the License Management Facility.
1-1
VMS Workstation Software Summary of New and Changed Features
___________________________
1.1.3 Hardcopy UIS-HCUIS
For Version 4.1, HCUIS has been incorporated into the
VWS kit. You need not install HCUIS separately.
NOTE: Because HCUIS is now incorporated into the
VWS base kit, the minimum block requirement for VWS
installation is 1200 more than was required with the
VWS Version 4.0 base kit installation.
__________________________________________________________________
1.2 New Features for VWS Version 4.1
___________________________
1.2.1 Tektronix 4125 Emulator
VWS Version 4.1 supports the Tektronix 4125 emulation
software (from here on, this is referred to as the
Emulator). For more detailed information on the
Emulator, refer to Using the VWS Tektronix 4125
Emulator and the Tektronix 4125 documentation.
NOTE: The UISBG.DAT file contains a "Create new TEK4125
window" section. When you create a TEK4125 terminal
window for the first time, this section is commented
out (! appears in the margin of each line). Edit the
UISBG.DAT file so that it appears as follows:
!
! The following is for the NEW creation of a TEK4125 terminal
! window
!
CHOICE "Create new TEK4125 window" -
/ROUTINE=UISBG$CREATE_PROCESS -
/IMAGE=SYS$SYSTEM:LOGINOUT.EXE -
/INPUT=SYS$MANAGER:VWS$TEK4125.COM -
/OUTPUT=NLA0: -
/ERROR=NLA0:
Be aware that the /INPUT statement in the above
example is subject to change if and when the Emulator
software changes.
1-2
VMS Workstation Software Summary of New and Changed Features
___________________________
1.2.2 Loading Fonts
A new set of .TEMPLATE files has been added to
SYS$FONT. This enables you to use the Courier (100
dpi) fonts in the terminal emulator while in 77 dpi-
mode. The Point and Spacing parameters are supplied
in the filenames as the 77 dpi equivalents. This, plus
the name RCOURIR, enable you to use the fonts as you
use any other terminal fonts. (See the VMS Workstation
Software User's Guide for more detailed information
about using terminal fonts.)
To load the fonts, rename the appropriate .TEMPLATE
files to .COM files and execute them. They are then
available for use by the terminal emulator. The
next time the system is booted, these files execute
automatically.
The list of .TEMPLATE files follows.
UIS$LOAD_FONT_RCOURIR_19X08.TEMPLATE
UIS$LOAD_FONT_RCOURIR_19X12.TEMPLATE
UIS$LOAD_FONT_RCOURIR_19X16.TEMPLATE
UIS$LOAD_FONT_RCOURIR_19X24.TEMPLATE
UIS$LOAD_FONT_RCOURIR_38X16.TEMPLATE
UIS$LOAD_FONT_RCOURIR_38X24.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_19X08.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_19X12.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_19X16.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_19X24.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_38X16.TEMPLATE
UIS$LOAD_FONT_RCOURIR_TCS_38X24.TEMPLATE
___________________________
1.2.3 ReGIS Plane Mask Support
The G$SET_PLANE_MASK GIDIS call is now modified to be
able to set the UIS plane mask. Plane mask now works
as specified in the ReGIS documentation.
1-3
VMS Workstation Software Summary of New and Changed Features
___________________________
1.2.4 New UIS Routines for VWS Version 4.1
o UIS$GET_PLANE_MASK
o UIS$SET_PLANE_MASK
See Section A.1 for a detailed description of the
above UIS routines.
___________________________
1.2.5 VT200 Terminal Emulator Color Map Changes
Prior to VWS V3.3, using the logical names UIS$VT_
PRIVATE_COLOR_MAP and UIS$VT_PLANE_COUNT was the only
way to specify size of the color maps to be used with
the VT200 terminal emulator. VWS V3.3 added two new
mechanisms for such color map size specification:
o A new qualifier to UISBG.DAT
o A new parameter to UIS$CREATE_TERMINAL
A plane count of zero specifies a monochrome (bitonal)
terminal. Monochrome terminals do not support ReGIS
applications.
A plane count greater than zero specifies a color
terminal.
NOTE: Color terminals use extra system overhead, so it
is preferable to use a monochrome terminal whenever
possible.
The logical names UIS$VT_PRIVATE_COLOR_MAP and UIS$VT_
PLANE_COUNT are still valid for $ASSIGNs (open) of
WTA0:.
1-4
VMS Workstation Software Summary of New and Changed Features
_____________________
1.2.5.1 Changes to UISBG.DAT for Color
Terminals
In the UISBG.DAT file, the new switch is:
/PLANE_COUNT=n
where: n=0,1,2,3,...8
o If the argument (n) is zero or the /PLANE_COUNT
qualifier is omitted, a monochrome terminal (that
is, a VT200 window that uses the shared global
colormap) is created.
o If n#0 (that is, 1#n#8), the value of n is the
PLANE_COUNT and a private colormap is created with
2[n] colormap entries.
NOTE: The logicals UIS$VT_PRIVATE_COLOR_MAP and UIS$VT_
PLANE_COUNT are ignored for terminal emulator windows
created via the Workstation Options menu.
NOTE: ReGIS is not available for terminals. The default
in the command file (UISBG.DAT) for the color windows
is n=3 planes.
_____________________
1.2.5.2 Changes to UIS$CREATE_TERMINAL for
Color Terminals.
An optional sixth parameter has been added to
UIS$CREATE_TERMINAL. This parameter is a pointer to
a terminal attributes list. The terminal attributes
list is a data structure that consists of longword
pairs. The first longword stores an attribute ID;
the second longword holds the attribute value. The
constant UIS$C_TERM_END_OF_LIST terminates the list.
Use the attribute ID UIS$C_TERM_COLOR to specify
a plane count. If you omit the UIS$C_TERM_COLOR
attribute, use the logicals UIS$VT_PRIVATE_COLOR_MAP
and UIS$VT_PLANE_COUNT to determine the type of window
created. An example C code fragment follows.
1-5
VMS Workstation Software Summary of New and Changed Features
# include <UISUSRDEF>
$DESCRIPTOR( termtype, "WT");
$DESCRIPTOR( title, "A terminal");
char *device[20];
int devnam[2];
int attributes = 0; /* Dummy attribute block */
int termattributes[3] = {UIS$C_TERM_COLOR, 2, UIS$C_TERM_END_OF_LIST};
devnam[0] = 20;
devnam[1] = &device;
UIS$CREATE_TERMINAL( &termtype,
&title,
&attributes,
&devnam,
&devnam,
&termattributes);
For direct calls to UIS$CREATE_TERMINAL, all functions
work the same way. However, if you want to control
the plane count, add the optional parameter (for
example, n=2 in the above C example). If the call
to UIS$CREATE_TERMINAL has no optional parameter, the
emulator functions as usual; it uses the values of the
logicals. This holds true also for terminals created
via an $ASSIGN-this functions as usual.
The PLANE_COUNT value overrides the logical UIS$VT_
PLANE_COUNT defined in the file UIS$SETUP_VT240.COM
for any ReGIS terminal windows created from the
Workstation Options menu. The logicals for the plane
count and private color map remain valid for $ASSIGNs
of WTA0: and for standard UIS$CREATE_TERMINAL calls.
1-6
VMS Workstation Software Summary of New and Changed Features
___________________________
1.2.6 Multilevel Device Interrupt Dispatching for Q22 Bus
Devices
VAX peripheral devices request interrupts at IPLs 20
through 23. IPLs 20 through 23 generally correspond to
the four bus request levels of the UNIBUS (BR4 through
BR7) and Q22 bus (BIRQ4 through BIRQ7).
Because the UNIBUS also has four bus grant lines (BG4
through BG7), interrupt dispatching for UNIBUS devices
occurs inherently at four levels. For example, when
a UNIBUS device requests an interrupt at BR4 from a
processor executing at an IPL lower than IPL 20, the
processor grants the interrupt to the device at IPL 20
(BG4). If the processor is already executing at IPL 20
or above, the device interrupt remains pending.
The MicroVAX 3600-series and MicroVAX II Q22 bus
architecture has only one bus grant line (BIAK). As
a result, the CPU must, by default, grant all Q22
bus device interrupts at a single IPL (IPL 23), even
though the CPU arbitrates interrupt requests according
to the bus request line used. For example, when a
Q22 bus device requests an interrupt at BIRQ4 from
a processor executing at an IPL lower than IPL 20,
the processor grants the interrupt, unconditionally
raising the IPL to IPL 23. If the processor is already
executing at IPL 20 or above, the interrupt remains
pending.
This implementation of interrupt dispatching on this
configuration and behavior of Q22 bus devices has the
following consequences:
1 Because the MicroVAX 3600 series and MicroVAX II
dispatch Q22 bus interrupt at a single IPL, Q22 bus
devices that request interrupts at a high BIRQ must
be positioned on the bus closer to the CPU than
devices that interrupt at a low BIRQ. (To determine
the BIRQ level of any given Q22 bus device, refer
to the hardware user's guide.)
1-7
VMS Workstation Software Summary of New and Changed Features
2 A Q22 bus peripheral that requests interrupts
at a low BIRQ might not grant an interrupt to a
peripheral that requests interrupts at a higher
BIRQ. For instance, the processor could grant an
interrupt to a BIRQ4 device, elevating its IPL to
IPL 23 in the process. While executing at IPL 23,
the processor would not grant the interrupt request
of a BIRQ7 device. In a real-time environment,
where I/O operations to one peripheral must always
have priority over lesser forms of I/O, this
behavior can cause problems.
The VWS video device driver interrupt service routines
contain code to avoid the problems just mentioned.
This code performs special checks for the legality
of the Q22 bus configuration and, if the Q22 bus
configuration is legal, lowers IPL to enable the
interrupts of higher priority devices.
This code performs checks to compare the device IPL
of the interrupting peripheral with the IPL in the
processor status longword (PSL) of the interrupted
thread of code. If the device IPL is not greater than
the IPL in the saved PSL, the driver generates an
ILLQBUSCFG bugcheck, signifying that the Q22 bus is
illegally configured.
In previous versions of VWS, this was not a fatal
bugcheck. Since an illegally configured Q22 bus can
cause the driver to fail in fatal ways, this is now a
fatal bugcheck.
_____________________
1.2.6.1 Ensuring That the Q22 Bus Is Properly
Configured
The bus architecture of the MicroVAX 3600 and MicroVAX
II requires devices with the ability to interrupt
at a high BIRQ level (for instance, BIRQ7) to be
positioned on the bus closer to the CPU than devices
that interrupt at lower BIRQ levels. In a Q22 bus
system, when the processor grants an interrupt to
a device, the processor passes the interrupt down
1-8
VMS Workstation Software Summary of New and Changed Features
the BIAK line to the first device on the bus. If the
device is not the one requesting an interrupt, it is
responsible for propagating the acknowledgment grant
to the next device on the bus, and so on. However, if
a device coincidentally initiates an interrupt just
before it would be required to pass the grant further
down the bus, it might instead "steal" the grant for
itself. The following two examples illustrate problems
with an illegally configured Q22 bus.
Consider the case of a device that interrupts at
BIRQ6 (IPL 22). Assume the CPU is at IPL 21. The
bus arbitrator grants the device its interrupt and
sends the grant down the Q22 bus. At the same time,
however, if a device that interrupts at BIRQ5 (IPL 21)
and is closer to the CPU on the grant path initiates
an interrupt, it might not propagate the grant as it
should. Instead, it might steal the grant and assume
ownership of the interrupt. Thus, an IPL 21 device
might successfully interrupt a processor executing at
IPL 21. The end result is an unpredictable break in
synchronization with many possible consequences.
Consider also an instance where the second device
interrupts at a lower IPL (for instance, BIRQ4 (IPL
20)). Although it is executing below the CPU IPL (IPL
21), this device can also steal the interrupt grant.
In this instance, because the VAX architecture does
not permit an REI from a lower to a higher IPL, the
break in synchronization results in a reserved operand
fault when the driver interrupt service routine issues
the REI instruction.
__________________________________________________________________
1.3 Changed Features for VMS Workstation Software Version
4.1
1-9
VMS Workstation Software Summary of New and Changed Features
___________________________
1.3.1 New Hardware Support
o VAXstation 3100
___________________________
1.3.2 132-Column Terminal Fonts
The 132-column terminal fonts have been replaced with
a new set of fonts. The new fonts have an improved
appearance.
NOTE: The old 132-column terminal fonts are still
available in the SYS$FONT directory.
Use of the new fonts is transparent to the terminal
emulator and to applications that use the DTABER font
names.
NOTE: Use of the DTERMIN font names might still result
in the old fonts.
___________________________
1.3.3 Debugger
The default behavior of the debugger on a workstation
has changed. Refer to the VMS Release Notes for more
detailed information.
___________________________
1.3.4 Printer Setup Options
The "Enter new print destination" of the Printer Setup
menu is disabled. To change the print destination,
assign the logical UIS$PRINT_DESTINATION to the
desired value.
For example:
$ DEFINE/SYSTEM/EXEC UIS$PRINT_DESTINATION "CSA0:"
NOTE: This will be addressed in a future release of
VWS.
1-10
VMS Workstation Software Summary of New and Changed Features
___________________________
1.3.5 SYS$FONT Logical Name
The definition of the SYS$FONT logical name is now
changed. It now translates to SYS$SYSROOT:[SYSFONT]
(rather than SYS$COMMON:[SYSFONT] as it did
previously). This is a search list that points to both
a system-specific directory and a common directory.
After you install VWS, review the contents of these
directories to make sure there are no duplications.
In most cases, you should keep all fonts in the common
directory.
1-11
_______________________________________________________
2 VMS Workstation Software Resolved Problems
This chapter describes VMS Workstation Software
problems that have been resolved since the VWS Version
4.0 release.
__________________________________________________________________
2.1 VMS Workstation Software Version 4.1 Resolved Problems
___________________________
2.1.1 UIS and UISDC Routines
_____________________
2.1.1.1 UIS$GET_LINE_WIDTH
Previously, if you chose UIS$C_WIDTH_WORLD as the
mode argument to the UIS$GET_LINE_WIDTH routine, the
routine would return 0.
This routine is now modified so if you choose UIS$C_
WIDTH_WORLD as the mode argument, the line width
specified from the routine UIS$SET_LINE_WIDTH is
returned in world coordinates.
_____________________
2.1.1.2 UIS$GET_OBJECT_ATTRIBUTES
In the past, improper extent values were returned when
this call was invoked with the flag UIS$M_DL_UPDATE_
WINDOW disabled. This is now corrected.
_____________________
2.1.1.3 UIS$SET_POINTER_PATTERN and
UISDC$SET_POINTER_PATTERN
It is now possible to bind the default cursor pattern
to an AST region. Previously, the calls:
UIS$SET_POINTER_PATTERN (VD_ID, WD_ID,,,,,,,UIS$M_BIND_POINTER)
or
UISDC$SET_POINTER_PATTERN (WD_ID,,,,,,,UIS$M_BIND_POINTER)
2-1
VMS Workstation Software Resolved Problems
produced the following error:
%UIS-W-NOURG, cannot disable region AST because no
matching region can be found.
Now it is possible to bind the default cursor pattern
to the AST region by using the UIS$M_BIND_POINTER
flag.
_____________________
2.1.1.4 UIS$SET_TB_AST
Problems relating to disabling AST routines in the
call to UIS$SET_TB_AST have been resolved.
_____________________
2.1.1.5 UISDC$EXECUTE_DOP_SYNCH
The symbol UIS$C_EFN_SYNCH defines the event flag used
by UISDC$EXECUTE_DOP_SYNCH. Use this symbol in the
call to the $SYNCH system service to synchronize with
the completion of UISDC$EXECUTE_DOP_SYNCH.
___________________________
2.1.2 User Interface
In the past, mouse hits on the borders and banners
of windows were sometimes ignored. This has been
corrected.
___________________________
2.1.3 Invalid Position Pointer Value
In some cases, the current position pointer value was
not properly tested. This caused it to become invalid
and eventually caused the workstation to hang. This is
now fixed.
2-2
VMS Workstation Software Resolved Problems
___________________________
2.1.4 Italian Keyboard
The layout table for the VWS Italian keyboard is
changed for the <CTRL/A> and <CTRL/Q> keys. The
definition of the <CTRL/A> and <CTRL/Q> keys is now
reversed in the Italian tables. The <CTRL/A> key
switches from insert to overstrike mode, and the
<CTRL/Q> key reenables keyboard output after the
<CTRL/S> key as in the North American keyboard tables.
___________________________
2.1.5 Shrink to Icon Operation Resulting in Process Hang
Under certain circumstances, the Shrink to Icon
operation could result in a process hang, a terminal
emulator window hang, or other error. This problem has
been_corrected.____________
2.1.6 Render Operation
Previously, if you rendered single points to a
PostScript printer, the points would not appear. Now
the points appear if the line cap is set to round.
_____________________
2.1.6.1 During DEBUG Startup
In some cases, when a user would generate a shrink to
live icon state at the same time DEBUG was starting
up, it was impossible to expand the icon after that.
What was happening was that DEBUG was sending an
OSC sequence that set up a MENU_AST and also set up
pointer ASTs. The code checked for inhibit but not for
real-time icons. This has been corrected.
___________________________
2.1.7 UIS$PRINT_DESTINATION
Since the Print Destination menu was removed in VWS
Version 3.3, the "Restore Last Saved Settings" option
has restored the print destination to CSA0 (or a
previously user-defined destination). This has now
been corrected so that the Restore Last Saved Settings
2-3
VMS Workstation Software Resolved Problems
option no longer affects the UIS$PRINT_DESTINATION
logical. Now, only a privileged user can redefine this
logical with a DEFINE statement.
___________________________
2.1.8 UISENTRY.H
A fix was made to UISENTRY.H because of an incorrect
declaration of UISDC$ALLOCATE_DOP. The correct
declaration is:
int *uisdc$allocate_dop();
___________________________
2.1.9 Late Delivery of ASTs
In the past, late delivery of ASTs associated with a
deleted window caused several hangs and crashes. This
problem has been corrected.
___________________________
2.1.10 SYSTEM PASSWORD
In VMS Workstation Software Version 3.2 and earlier,
if a systemwide password (not to be confused with
the password for the system account) was enabled,
no terminal window would appear and no error message
would display.
In VMS Workstation Software Version 4.1, this is
corrected. This setting is ignored for terminal
emulator windows; however, the system password is
required for other (non-emulator) terminals.
2-4
_______________________________________________________
3 VMS Workstation Software Problems and Restrictions
This chapter describes problems and restrictions you
might encounter when using VMS Workstation Software
Version 4.1.
__________________________________________________________________
3.1 VWS Startup Procedure in New Location
For Version 4.1, the VWS startup procedure is now
located in SYS$STARTUP:STARTVWS.COM, rather than in
SYS$MANAGER:STARTVWS.COM where it used to be.
If you invoke STARTVWS.COM from SYSTARTUP_V5.COM, the
change in location will already be updated for you
by the installation. If, however, you start the VWs
software from some other procedure, you must make the
change yourself.
NOTE: The old STARTVWS.COM procedure in SYS$MANAGER is
not deleted, so if you have specific commands there
that you want to include in the latest STARTVWS.COM,
edit the STARTVWS.COM in SYS$STARTUP to include them.
NOTE: It is not absolutely necessary to run the
VWS$EMULATORS process for Version 4.1. This has been
commented out of the new STARTVWS.COM procedure.
__________________________________________________________________
3.2 AUTOGEN Problem
If you are running 100 DPI fonts, AUTOGEN incorrectly
handles the setting of the TTY_DIALTYPE parameter for
VWS V4.1.
3-1
VMS Workstation Software Problems and Restrictions
To work around this problem, add the following entry
in SYS$SYSTEM:MODPARAMS.DAT:
TTY_DIALTYPE = 160
__________________________________________________________________
3.3 Mouse Inoperative on Fast Processors
Sometimes, after you reboot the system, VWS ignores
input (position and/or button changes) from the mouse.
Until this problem is corrected, take the following
steps to make the mouse operative:
1 Unplug the mouse, then plug it back in.
2 If the mouse continues to be inoperative, go to
Step 3.
3 Shut down VMS and reboot without cycling power.
4 If the mouse continues to be inoperative, repeat
these steps.
__________________________________________________________________
3.4 ReGIS Restrictions
The terminal emulator implementation of ReGIS includes
several restrictions. See VMS Workstation Software
User's Guide, Appendix B, "ReGIS Implementation" for a
full description of ReGIS restrictions.
__________________________________________________________________
3.5 Fonts Loaded By Default and Slow Painting of Popped
Windows
Several factors can cause popped windows to paint
slowly on GPX and color VAXstation 2000 systems. The
following situations contribute to this problem:
o Having a large number of fonts loaded.
o Having a large number of windows (and/or large-
sized windows) on the screen.
3-2
VMS Workstation Software Problems and Restrictions
To ease this problem, evaluate which fonts you load at
system startup. By default, VMS Workstation Software
starts up with only the necessary fonts. If you
want larger fonts, rename the files in SYS$FONT from
UIS$LOAD_FONT*.TEMPLATE to UIS$LOAD_FONT*.COM.
NOTE: Rename only the files that contain fonts you want
to use.
The command files in SYS$FONT called UIS$LOAD_
FONT*.COM are executed at startup. You can rename a
.COM file to .TEMPLATE to prevent the font from being
loaded. Conversely, when you want to enable the font
for loading, rename the .TEMPLATE to .COM.
NOTE: The technical character set fonts are loaded as
supplied (UIS$LOAD_FONT_TCS*.COM).
In addition, the Technical Character Set fonts are
loaded by default. If you do not normally use these
fonts, rename the UIS$LOAD_FONT_TCS*.COM files in
SYS$FONT to UIS$LOAD_FONT_TCS*.TEMPLATE.
A complete list of fonts included with the VMS
Workstation Software kit is provided in the VMS
Workstation Software Installation Guide, Appendix
A. Check that list to make sure you are not
overburdening your system with unneeded fonts. Delete
any unnecessary fonts from your system.
__________________________________________________________________
3.6 Print Destination Restriction
There is now a restriction on the use of the Enter
new print destination option of the Printer Setup
menu. See VMS Workstation Software User's Guide,
Chapter 2, "Changing Print Destination" for a detailed
explanation of this restriction.
3-3
VMS Workstation Software Problems and Restrictions
__________________________________________________________________
3.7 Color VAXstations in a Cluster Environment
When you boot a VAXstation II/GPX with an alternate
console terminal in a cluster environment, the
hardware initialization might take so long that
the cluster connection is lost. To prevent
this occurrence, increase the SYSGEN parameter
RECNXINTERVAL to 40 seconds on all nodes in the
cluster.
__________________________________________________________________
3.8 SET HOST/DTE
If you use the VMS feature SET HOST/DTE in conjunction
with the Hold Screen key or <CTRL/S>, the process
could exhaust its process address space. When VMS
Workstation Software tries at that point to allocate
memory, there is none available and the system can
crash.
__________________________________________________________________
3.9 Setting of TTY_CLASSNAME SYSGEN Parameter
During VMS V5.0 Field Test 1, a VWS-specific version
of the terminal class driver (VZDRIVER) was used. This
has been discontinued. The VWS installation procedure
will set the TTY_CLASSNAME SYSGEN parameter back to
"TT".
__________________________________________________________________
3.10 Setting of MULTIPROCESSING SYSGEN Parameter
VWS does not support multiprocessing synchronization.
The SYSGEN parameter MULTIPROCESSING should not be set
to two. (Two is not the default value.)
__________________________________________________________________
3.11 User Interface
The following sections describe problems and
restrictions in the user interface.
3-4
VMS Workstation Software Problems and Restrictions
___________________________
3.11.1 VAXstation II/GPX Boot Problem
If your VAXstation II/GPX system is unresponsive
during a boot or shutdown operation, press the F2
key. The system may have written a message to the
operator console window and may be waiting for you
to read the message before it continues. The operator
console window stays activated only for 30 seconds.
This restriction prevents the possibility of hanging
your workstation.
___________________________
3.11.2 Restriction with Autologin
If you log in to your first terminal emulator window
while autologin is enabled and then quickly create
another emulator, you may not be automatically logged
in to the second window. This is because the process
information for the first window has not yet been
saved. A solution is to wait until the initial login
procedure has executed before creating additional
terminal emulator windows.
__________________________________________________________________
3.12 Programming Interface
The following sections describe problems and
restrictions in the programming interface.
___________________________
3.12.1 UIS$C_TEXT_WRITE-16-Bit Text Problem
When you use text with control lists and 16-bit
text (for example, 2-byte Kanji fonts), the control
list item UIS$C_TEXT_WRITE should have a value that
specifies the number of characters it will write. VWS
interprets this value as the number of bytes VWS will
write instead. To avoid this problem when you use 16-
bit text, specify double the number of characters you
want to write as a value for the control list item.
3-5
VMS Workstation Software Problems and Restrictions
___________________________
3.12.2 UIS$CIRCLE and UIS$ELLIPSE-Overflow Problem
On both VAXstation II and VAXstation II/GPX systems,
UIS$CIRCLE or UIS$ELLIPSE might draw certain circles
or ellipses incorrectly. Specifically, non-whole
(those with different starting and ending angles),
filled ellipses might be drawn incorrectly during
close zooms.
___________________________
3.12.3 UIS$DISABLE_KB and UIS$DISABLE_VIEWPORT_KB-AST Not
Delivered
When a virtual keyboard is disabled by a UIS$DISABLE_
KB or UIS$DISABLE_VIEWPORT_KB, the Lose Keyboard AST
routine will not be delivered. If your application
depends on this AST being received after the virtual
keyboard has been detached from the physical keyboard,
you must explicitly call the AST routine after
disabling the keyboard.
___________________________
3.12.4 UIS$EXTRACT_OBJECT-Incorrect Length Returned
If you call UIS$EXTRACT_OBJECT with just the obj_id
and retlen arguments, and private data is associated
with the object, an incorrect length is returned.
(It will be the length of the object rather than the
length of the object plus the private data.)
To work around this problem, call UIS$PRIVATE with
just the obj_id and retlen arguments to ascertain the
length of the private data. Add that to the length
returned by UIS$EXTRACT_OBJECT to ascertain the length
of the entire object.
3-6
VMS Workstation Software Problems and Restrictions
___________________________
3.12.5 UIS$HSV_TO_RGB-Saturation Parameter = 0.0
When you call the UIS$HSV_TO_RGB routine with the
saturation parameter equal to 0.0, you must set the
hue parameter to a floating point value of -1.
___________________________
3.12.6 UIS$SET_KB_ATTRIBUTES-Spurious Data
When you are using the Up/Down key transitions enabled
by UIS$SET_KB_ATTRIBUTES, you may get spurious data
when the physical keyboard is attached to the window.
A possible solution is to ignore incoming data for a
short time after getting a GAIN_KB_AST. This will be
fixed in a future release.
___________________________
3.12.7 UIS$SET_POINTER_AST-Late Execution of Exit AST
Routines
When two contiguous regions have been set up with
UIS$SET_POINTER_AST, you might execute an exit AST
intended for the previous region after executing the
first movement AST routine for the new region.
To clarify, when you exit from one region and enter
the other, three actions occur in the following order:
1 The last movement in the first region
2 Exiting from the first region
3 The first movement in the new region
However, the ASTs associated with these actions may be
delivered out of order: last movement, first movement,
exit.
The recommended solution is to test for the first
movement on any contiguous region and emulate the
exit AST before taking any other action. According
to the application, you may wish to emulate only some
3-7
VMS Workstation Software Problems and Restrictions
essential portion of the exit AST routine and let the
actual AST perform the remainder when it is executed.
___________________________
3.12.8 Drawing Images That Use Eight Bits/Pixel
When drawing images that use eight bits/pixel, use the
COPY writing mode (UIS$C_MODE_COPY) to use the pixel
values as direct indexes into the color map. This
writing mode will copy each pixel value from the image
into the bit map without any changes to the data.
The default writing mode (UIS$C_MODE_OVER) will not
work like COPY mode.
__________________________________________________________________
3.13 Text Problems
The following sections describe problems and
restrictions to using text with the programming
interface.
___________________________
3.13.1 Extracting Transformed Control Lists
The result of extracting transformed control list
text is undefined. That is, the following sequence
of routine calls will produce a buffer containing
unpredictable results:
UIS$TEXT(vd_id, atb, text_string, x, y, ctllist, ctllen)
obj_id = UIS$GET_CURRENT_OBJECT(vd_id)
UIS$TRANSFORM_OBJECT(obj_id, matrix, atb)
UIS$EXTRACT_OBJECT(obj_id, buflen, bufaddr, retlen)
NOTE: The results on the screen and within the UIS
internal display list are correct.
3-8
VMS Workstation Software Problems and Restrictions
___________________________
3.13.2 Tabs in Control Lists
Text that has a control list containing relative or
absolute tabs may produce unexpected results if the
text falls under any of the following categories:
o Sloped
o Written with a non-default major text path (for
example, UIS$C_TEXT_PATH_LEFT)
o Transformed (using UIS$TRANSFORM_OBJECT or
UIS$COPY_OBJECT) to be sloped
Slanted text that has a control list containing
relative or absolute tabs may erase portions of
characters when written with any writing mode that
writes the background, such as overlay negate.
___________________________
3.13.3 Text Placement and Display Lists
After calling UIS$TEXT and UIS$NEW_TEXT_LINE to create
lines of text, you may wish to insert more text at the
end of a line. Since text position is undefined when
you insert text into a display list, you should always
explicitly position your inserted text.
___________________________
3.13.4 Text Formatting Problems
The following sections describe problems and
restrictions when formatting text.
Enabling and Disabling Text Formatting
If the original input attribute block for a UIS$TEXT
or UISDC$TEXT call with a control list does not have
text formatting enabled and a subsequent ATB in
the control list does format text, the results are
undefined.
3-9
VMS Workstation Software Problems and Restrictions
Formatted Text with Non-default Attributes
Formatted text gives undefined results if the text or
vertical major text path being written has non-default
attributes of slant, slope, rotation, or character
size. The same is true for formatted text that is
transformed to have non-default attributes of slant,
slope, rotation, or character size.
Full Text Justification of Nonstandard Fonts
For fully justified text to work correctly with fonts
other than those supplied on the distribution kit,
the glyph for the space character must be in the 33rd
position in the font, which is the same position as
the ASCII space character in the supplied fonts.
___________________________
3.13.5 Sloped Text
The following sections describe the behavior of sloped
text when it is viewed through a distorted viewport.
Text Slope Angles with Distorted Windows
If sloped text is displayed using UIS$TEXT and a
distorted window/viewport mapping (that is, the aspect
ratio of the window differs from the aspect ratio
of the viewport), the results differ, depending on
whether character scaling is enabled. If character
scaling is not enabled, the angle is displayed
relative to the device. For example, at a slope of
45 degrees (with major path right), each character
position moves up and right by the same number of
pixels. If character scaling is enabled, the slope is
measured relative to world coordinates. For example,
at a slope of 45 degrees (with major path right),
each character position moves up and right by the same
world-coordinate amount.
3-10
VMS Workstation Software Problems and Restrictions
If sloped text is displayed using UISDC$TEXT, the
slope angles are measured based on device coordinates,
regardless of whether scaling is enabled.
This behavior is permanent and is consistent with
other uses of unscaled text and UISDC routines with
distorted viewport/window mappings.
Text Slope Angles on VR100 Monitors
If sloped text is displayed using UIS$TEXT with
character scaling disabled, the angles appear to be
distorted, even if the viewport and window aspect
ratios are the same. The reason for this behavior is
that the angle is being drawn in device coordinates,
and pixels on a VR100 are not square. To make the
angle appear correct, you must enable character
scaling, using the UIS$SET_CHAR_SIZE routine.
If sloped text is displayed using UISDC$TEXT, angles
appear distorted on a VR100 monitor.
This behavior is permanent and is consistent with
other uses of unscaled text and UISDC routines with
VR100 monitors.
Note: The only supported hardware device that uses a
VR100 monitor is a VAXstation I.
___________________________
3.13.6 Restrictions on Writing Modes That Change the
Background
Scaled Text-GPX and VAXstation 2000 Systems
When the VAXstation II/GPX or color VAXstation 2000
scales text, distortion can occur as a result of
the hardware's inability to scale properly to non-
integer values. If you are using a writing mode
that changes background pixels (for example, REPL
or REPLN), the foreground pixels can be overwritten.
3-11
VMS Workstation Software Problems and Restrictions
This can result in what appears to be missing pixels
in scaled characters. This problem occurs more often
with proportionally spaced fonts than with monospaced
fonts. If text is drawn at slope, rotation, or slant
angles that are not zero or multiples of 90 degrees,
scaling is done implicitly.
This is a permanent restriction.
Scaled Text-All Systems
If text is written in a mode that causes the
background of the cell to be written (for example,
REPL or REPLN), unwritten pixels might exist between
adjacent character cells. If text is drawn at slope,
rotation, or slant angles that are not zero or
multiples of 90, scaling is done implicitly.
This is probably an unavoidable effect of
rasterization, but investigation of possible future
improvements continues.
__________________________________________________________________
3.14 Device Driver Interface
___________________________
3.14.1 MOVE/ROTATE DOP-Specifying Scaling
There is a problem in specifying scaling in the
MOVE/ROTATE Drawing Operation Primitive (DOP).
If the source_width divided by the vec1_length or the
source_height divided by the vec2_length cannot be
represented exactly in 12 bits or fewer, a pixel may
be dropped from the end of the source.
The recommended solution is to decrease the vector
length (usually by a constant 1 or 2 pixels), without
changing the Dx or Dy values, until the full source is
drawn correctly.
3-12
VMS Workstation Software Problems and Restrictions
___________________________
3.14.2 Using DOPs with UISDC$SET_CLIP
When you use DOPs and the routine UISDC$SET_CLIP,
the DOP returned from the routine UISDC$ALLOCATE_DOP
contains incorrect values for the viewport clipping
rectangle.
The recommended workaround for this problem is to
change the values within the DOP immediately after it
is allocated, as shown in the following example.
dop = uisdc$allocate_dop (&wdid, &dop_size, &1);
dop->dop$w_vp_min_x = dop->dop$r_fill_9.dop$r_fill_10.dop$w_delta_x - 6;
dop->dop$w_vp_min_y = dop->dop$r_fill_9.dop$r_fill_10.dop$w_delta_y - 6;
dop->dop$r_fill_9.dop$r_fill_10.dop$w_vp_max_x += dop->dop$w_vp_min_x;
dop->dop$r_fill_9.dop$r_fill_10.dop$w_vp_max_y += dop->dop$w_vp_min_y;
__________________________________________________________________
3.15 System Management Interface
SYSTEM Account Must Be Usable to Load the VMS
Workstation Software Correctly
If the SYSTEM account is not usable, the VMS
Workstation Software does not load correctly when you
reboot the VAXstation hardware. Loading fails when the
password for the SYSTEM account is expired. To update
the password for the SYSTEM account, invoke the VMS
Authorize Utility (AUTHORIZE).
__________________________________________________________________
3.16 User Interface
RESIZE WINDOW Time-Out Implemented
The RESIZE WINDOW feature has been modified so that
it stays activated for 30 seconds. This restriction
prevents the possibility of hanging your workstation.
3-13
VMS Workstation Software Problems and Restrictions
Receiving Operator Messages in a Local Area VAXcluster
When your workstation is a member of a Local Area
VAXcluster, its operator window is disabled by
default. DIGITAL recommends that you do not re-enable
the operator window. Instead, to monitor operator
messages, create a terminal emulator window and enter
the REPLY/ENABLE command at the DCL prompt ($). To
execute the REPLY/ENABLE command, you must have the
OPER privilege.
SET PROCESS/SUSPEND Command Can Cause Your Workstation
to Hang
Entering the SET PROCESS/SUSPEND command to suspend
a workstation process that creates windows can cause
your workstation to hang. That is, no further display
operations are executed.
The locks control the process access to the
workstation display. When you use the SET
PROCESS/SUSPEND command to suspend a process that
currently holds a lock, the process cannot give up its
display lock, thereby preventing other processes from
accessing the display.
To return your workstation to normal operation,
enter the SET PROCESS/RESUME command, specifying the
suspended process.
__________________________________________________________________
3.17 Programming Interface
VWSSYSDEF.H Contains Syntax Errors
If you select the C language option in the
installation procedure, the resulting VWSSYSDEF.H
file contains syntax errors. These syntax errors cause
compiler warnings when you include the VWSSYSDEF.H
file in your program.
3-14
VMS Workstation Software Problems and Restrictions
To avoid these compiler warnings, edit the file to
remove the dimension specification ("[1]") from the
declarations of the following structures:
dop_point_array
dop_line_array
dop_ftext_array
dop_vtext_array
dop_poly_array
dop_image_array
dop_move_array
dop_move_r_array
dop_mvr_array
SYS$SUSPEND Calls Can Cause Your Workstation to Hang
Calling the SYS$SUSPEND system service to suspend a
workstation process that creates windows can cause
your workstation to hang. That is, no further display
operations are executed.
The locks control the process access to the
workstation display. When you use the SYS$SUSPEND
system service call to suspend a process that
currently holds a lock, the process cannot give up
its display lock, thereby preventing other processes
from accessing the display.
To return your workstation to normal operation, issue
a SYS$RESUME system service call, specifying the
suspended process.
Undesirable Visual Effects Caused by Hardware Replay
to a Previously Occluded Area of the VAXstation II/GPX
Display
On a VAXstation II/GPX, the VMS Workstation Software
uses two methods to restore occluded windows that have
become exposed. Its first method is to specify that
the GPX hardware "replay" the list of commands that
generated the graphics in the occluded area. When the
list of commands gets too long, the VMS Workstation
3-15
VMS Workstation Software Problems and Restrictions
Software switches to its second method, which saves
the screen contents in the occluded area and copies
them to the display when the occluded area is exposed.
In some applications, the first replay method causes
undesirable visual effects. To avoid these undesirable
visual effects, execute a scrolling operation within
the viewport. The scrolling operation causes the VMS
Workstation Software to switch from the replay method
to saving the screen contents in the occluded area.
To execute a scrolling operation in the viewport, you
can either make a call to UIS$MOVE_WINDOW or, if you
are using the DOP interface, queue a SCROLL_AREA DOP.
You should specify the same world coordinates in the
move window call that you specified when you created
the window.
The following FORTRAN code segment demonstrates how
to disable hardware replay when restoring an occluded
window:
WD_ID = UIS$CREATE_WINDOW(VD_ID,0.,0.,1.,1.,20.,20.) !Create window
CALL UIS$MOVE_WINDOW(VD_ID,WD_ID,0.,0.,1.,1.) !Disable replay
___________________________
3.17.1 Specifying a Negative Value As Start_deg or End_deg
Causes Incorrect Drawing of a Circle or Ellipse
If you specify a negative value as the start_deg or
end_deg parameter for a circle or ellipse, it is drawn
incorrectly. To achieve the desired drawing results
when specifying a negative value for either of these
parameters, do the following:
1 Take the negative value modulo 360 and add 360.
2 Specify the resulting value as the start_deg or
end_deg parameter.
3-16
VMS Workstation Software Problems and Restrictions
The following FORTRAN code segment demonstrates how to
change a negative value into a value that causes the
system to execute the drawing operation correctly:
START_DEG = AMOD(START_DEG,360.)+360.
END_DEG = AMOD(END_DEG,360.)+360.
CALL UIS$CIRCLE(VD_ID,ATB,X,Y,RADIUS,START_DEG,END_DEG)
3-17
_______________________________________________________
A Description of New Routines
__________________________________________________________________
A.1 New VWS Version 4.1 UIS Routines
A-1
New UIS Routines
UIS$GET_PLANE_MASK
_______________________________________________________
UIS$GET_PLANE_MASK
Returns the planes to be written to.
_______________________________________________________
FORMAT
UIS$GET_PLANE_MASK vd_id, iatb
_______________________________________________________
RETURNS
VMS Usage: plane_mask
type: mask_longword (unsigned)
access: write only
mechanism: by reference
The 32-bit bitmask that represents the planes to
be written to. This is acquired by accessing the
appropriate field within the ATB. This is returned
in R0.
_______________________________________________________
ARGUMENTS
vd_id
VMS Usage: identifier
type: longword (unsigned)
access: read only
mechanism: by reference
Virtual display identifier. The vd_id argument is
the address of a longword that uniquely identifies a
virtual display.
iatb
VMS Usage: longword_unsigned
type: longword (unsigned)
access: read only
A-2
New UIS Routines
UIS$GET_PLANE_MASK
mechanism: by reference
Input attribute block number. The iatb argument is
the address of a longword integer that identifies an
attribute block to be modified.
_______________________________________________________
DESCRIPTION
UIS$GET_PLANE_MASK returns the planes that are to
be written to. This information is obtained from the
specified iatb block. The plane mask value obtained
affects the planes within the virtual color map.
A-3
New UIS Routines
UIS$SET_PLANE_MASK
_______________________________________________________
UIS$SET_PLANE_MASK
Specifies the planes to be written to.
_______________________________________________________
FORMAT
UIS$SET_PLANE_MASK vd_id, iatb, oatb, plane_mask
_______________________________________________________
ARGUMENTS
vd_id
VMS Usage: identifier
type: longword (unsigned)
access: read only
mechanism: by reference
Virtual display identifier. The vd_id argument is
the address of a longword that uniquely identifies a
virtual display.
iatb
VMS Usage: longword_unsigned
type: longword (unsigned)
access: read only
mechanism: by reference
Input attribute block number. The iatb argument is
the address of a longword integer that identifies an
attribute block to be modified.
oatb
VMS Usage: longword_unsigned
type: longword (unsigned)
access: read only
mechanism: by reference
A-4
New UIS Routines
UIS$SET_PLANE_MASK
Output attribute block number. The oatb argument is
the address of a longword that identifies a newly
modified attribute block.
plane_mask
VMS Usage: mask_longword
type: mask (longword)
access: read only
mechanism: by reference
Specifies the planes that are to be written to.
_______________________________________________________
DESCRIPTION
UIS$SET_PLANE_MASK returns the planes that are to be
written to. Altering the plane mask affects the planes
within the virtual color map.
A-5
_________________________________________________________________
Index
_______________________________ _______________________________
A P
_______________________________ _______________________________
Autologin, 3-5 Programming Interface
_______________________________ problems and restrictions,
3-5
B
_______________________________ _______________________________
BIRQ level, 1-8 Q
Bus grant, 1-8 _______________________________
_______________________________ Q22 bus
rules for configuring, 1-8
D to 1-9
_______________________________
Driver Interface _______________________________
problems and restrictions, R
3-12 _______________________________
_______________________________ RESIZE WINDOW time-out, 3-13
E _______________________________
_______________________________ S
End_deg parameter _______________________________
specifying negative value SET PROCESS/RESUME command,
for, 3-16 3-14
_______________________________ SET PROCESS/SUSPEND command,
3-14
O Start_deg parameter
_______________________________ specifying negative value
Occluded area for, 3-16
restoring upon exposure, SYS$RESUME system service,
3-15 3-15
Operator messages SYS$SUSPEND system service,
receiving in a Local Area 3-15
VAXcluster, 3-14
Operator window, 3-14
Index-1
Index
_______________________________
T problems and restrictions,
_______________________________ 3-4
Tabs, 3-9 _______________________________
Text Formatting, 3-9 V
Text Problems, 3-8 _______________________________
_______________________________ VAXstation 2000, 3-11
U VAXstation II/GPX, 3-5, 3-6,
_______________________________ 3-11, 3-15
UIS$GET_PLANE_MASK, A-2 VMS Workstation Software
UIS$SET_PLANE_MASK, A-4 loading, 3-13
User Interface VWSSYSDEF.H
corrections to, 3-14
Index-2