| Previous | Contents | Index |
This section discusses restrictions and problems related to the DECterm
application.
1.9.9.1 Maximum Number of DECterm Windows
V1.2--4
A DECterm controller can create a maximum of 23 DECterm windows. This occurs because DECterm needs an event flag for each terminal window to use. There are 23 event flags that DECterm can use. (Event flag 0 and event flags 24--32 are not available for DECterm to use.)
If you need more than 23 DECterm windows, then you must create a new controller. To create a new controller, enter the following command:
$ MCR DECW$TERMINAL |
Note that the window from which this command is executed cannot be used
for anything else because this command does not return until the last
DECterm window is closed. After starting the controller with this
method, the user can create another 23 DECterm windows with the DCL
command CREATE/TERMINAL.
1.9.9.2 Changing the Auto Repeat Setting
V1.2--3
You cannot change the Auto Repeat setting in the DECterm Keyboard
Options dialog box. Instead, change the setting in the Keyboard dialog
box in the Session Manager.
1.9.9.3 Positioning DECterm
V1.2--3
If the resource Mwm*clientAutoPlace is set to True, DECterm windows are
not displayed where the DECW$TERMINAL.x and DECW$TERMINAL.y resources
are specified. As a workaround, set this resource to False and restart
MWM.
1.9.9.4 User Font Selection
V1.2
DECterm allows you to select available fonts from the Options/Window dialog box. A different font can be selected to replace the default Big Font, default Little Font, or default German Standard Font.
In the Options/Window dialog box, you can select the default font or enter the name of a font into a text field and select that font. When the Big Font, Little Font, or German Standard Font is selected and the Other toggle button for the font is selected, DECterm attempts to locate and use the font name supplied in the adjacent text field. For information on font naming conventions or fonts available on your system, consult your system manager.
Not all fonts work properly with DECterm. DECterm emulates a character-cell terminal, and, therefore, expects the fonts to be monospaced (each glyph occupies the same number of pixels). Proportional fonts can be chosen, but they produce unpredictable results. Furthermore, DECterm fonts are supplied in families of 26 related fonts, including variations for bold, double-width, double-width/double-height, normal, and condensed characters. Also, DECterm fonts include special characters, such as the Line Drawing and the DIGITAL Technical character sets. A DECterm font family is identified by the font naming convention. Use of fonts that do not have all the related font family variations, fonts that do not have the needed special characters, or font families that do not adhere to the DECterm font family naming conventions, may not result in an optimal display or otherwise perform as expected. |
On OpenVMS systems, Version 6.1 or higher, the VT330 font has been made available. The VT330 font is based on the 10x20 font used in the VT330 and VT340 terminals. Use this font on a system where they are available by entering the following font-name strings in the font-name text field:
-DEC-VT330-*-*-*--20-*-*-*-c-*-*-*
|
V1.2
DECterm supports a local echo mode. In the Options/General dialog box,
select Local Echo, which causes all character sequences generated
locally to be echoed on the display and passed to the remote host. This
feature is useful when connected to a host that does not echo typed
characters.
1.9.9.6 Answerback Message
V1.2
A user interface is available to enter answerback messages. This answerback message field is for compatibility with DIGITAL terminals.
The answerback field is a buffer that contains up to thirty characters. The answerback field in earlier DIGITAL terminals contained a message used to identify itself to the host system. For DECterm windows, the answerback field can be used to store a sequence of characters that you can use for any repetitive purpose.
A field is provided in the Options/General dialog box to enter answerback text. Click on the answerback field and enter your text. To enter control characters, encode the control character as a two-digit hex ASCII code, preceded by a number sign (#).
For example, when you enter #0D in the answerback field, DECterm responds with a carriage return.
If two consecutive number sign characters are entered (##), a single number sign is transmitted.
If anything other than a valid two-digit hex code or another number sign is detected after an initial number sign, the number sign is treated as a normal text character. Refer to any ASCII table for a complete list of characters.
The answerback text can also be concealed. When the Conceal Answerback
button is enabled, the answerback message is concealed. To deselect the
Conceal Answerback button, click on the answerback text field, which
erases the previous answerback message.
1.9.9.7 Seven-Bit Printer Support
V1.2
When the 7-Bit Printer button is selected in the Options/Printer dialog box, DECterm modifies printed text to be compatible with printers that do not support 8-bit characters. This includes modifying control sequence introducer (CSI) strings to use the format Escape-Left Bracket rather than the single 8-bit CSI character.
When the 8-Bit Printer button is selected, DECterm allows the use of 8-bit characters when printing. This mode can cause problems for older printers if they can not interpret 8-bit characters.
The default is 8-Bit.
1.9.9.8 VT330 and VT340 Terminal Emulation
V1.0
DECterm incorporates some of the features of the VT330- and VT340-series video terminals, such as ReGIS and Sixel graphics. DECterm does not provide complete VT330 and VT340 terminal emulation.
The following restrictions apply to DECterm:
V1.0
The /PROCESS=procnam qualifier does not work when used in conjunction with the /DETACHED qualifier, unless there is already a process running on the system where its process name is equal to the user name.
To work around this problem, use the following command procedure:
$! CREATE_TERM_PROC.COM
$!
$! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname
$!
$ SET NOON
$!
$! Set Process name to username
$!
$ X = F$CONTEXT("PROCESS", PID, "PRCNAM", "''F$PROCESS()'","EQL")
$ NAME = F$EDIT(F$GETJPI(X,"USERNAME"),"COLLAPSE")
$ SET PROCESS/NAME="''NAME'"
$ CREATE/TERMINAL/DETACHED/PROCESS="''P1'"
$!
$! Allow new process to RUN LOGINOUT before exiting subprocess
$ WAIT 00:00:10
|
If the /PROCESS=procnam qualifier specifies a process name that is already in use, the DECterm is created but creation of the process inside the DECterm fails. In this case, the DCL command CREATE/TERMINAL returns the following error message:
Duplicate process name |
V1.1
Printing to a port device requires you to have read and write privileges on that port. You cannot print by allocating the device, since the controller requires access to the device. Instead, set the device to WORLD:RW.
For example, to use the printer port on a VAX 3100 system, enter the following command from a privileged account or include the command in the system startup file:
$ SET PROTECTION=WORLD:RW TTA3:/DEVICE |
V1.1
The following information is specific to DECterm graphics:
V1.1
You cannot create more terminal windows than your system resources and quotas allow. If you have insufficient resources, a dialog box is displayed with a message indicating that no additional DECterm windows can be created.
To reduce the memory requirement of each DECterm window and create additional terminal windows, decrease the number of Record Lines Off Top in the Display dialog box and decrease the number of columns for each DECterm window.
Once the resource limit is reached, log out of all DECterm windows that
are running on the host system before you increase the number of
terminal windows.
1.9.9.13 Diagnostic Crash File and Messages
V1.1
DECterm produces a diagnostic file when a status code of fatal is returned. The DECTERM_ERROR.LOG file is produced in the login directory when the DECterm application exits abnormally. If you have a problem with the DECterm application and submit a Software Performance Report (SPR), include a copy of the log file. Under certain circumstances, a log file is generated even when no problem is encountered. Therefore, the appearance of a log file as an isolated event should not be cause for a problem report.
You can enable additional levels of diagnostic messages by defining either a logical name or a symbol named DECTERM_DIAG. When defined, enhanced diagnostics are displayed by the DECterm images. Use this mode only for diagnosing problems; it causes Session Manager message windows to be generated for each new DECterm created from the Session Manager.
DECterm diagnostics can be captured in a file by defining the logical
name DECW$TERMINAL_OUTPUT to point to a file.
1.9.9.14 ReGIS Locator Report
V1.0
When DECterm sends a ReGIS locator report in response to the R(P(I)) command, or in multiple input mode and the locator position is outside the addressable area, DECterm sends a locator report with the coordinates omitted. For example, press the A key to generate the report:
A[]<CR>, where <CR> is a carriage return (ASCII code 13). |
V1.1
The DECW$CDPLAYER application in the DECW$EXAMPLES directory requires
PHY_IO and DIAGNOSE privileges to operate the compact-disc player
hardware. Either your process or the image must have these privileges.
1.9.11 DECwindows Mail
This section contains information about the DECwindows Mail application.
1.9.11.1 DECwindows Mail Problems with MB3
V1.2--5
If you use MB3 to move a mail message, the DECwindows Mail application can become corrupted and the application can eventually crash. This problem happens if the primary selection is not in DECwindows Mail's main window.
As a workaround, always use MB1 to select a message before moving it. If the display becomes corrupted, restart DECwindows Mail.
The mail messages and mail folders themselves are not corrupted; only the display is corrupted. |
V1.2--4
In DECwindows Mail, if the user selects one or more messages in the
directory window using MB1 and then clicks on MB2 in another window
(such as a DECterm window), the entire contents of the selected
messages is pasted into the other window. The selected messages are
highlighted in the directory window, however the text of the selected
and pasted message is not highlighted in the Read window.
1.9.11.3 Responses to Keyboard Actions
V1.2--3
Enhancements in the DECwindows Mail application to comply more closely with OSF/Motif style conventions cause some changes with application responses to keyboard actions. Note the following changes.
If you use the Tab key to advance through text entry boxes in the Create/Send window, the current field is no longer highlighted. To select a field, use one of the standard Motif actions, such as double or triple clicking MB1, or use the Shift+Alt -> key sequence.
In several dialog boxes, press either the Select key or the space bar
to activate a pushbutton through the keyboard. Note that the Return key
and the Enter key are bound to other widgets in the dialog box.
Alternatively, you can continue to click MB1 to activate a pushbutton.
1.9.11.4 Using the Color Customizer with DECwindows Mail
V1.2
If you use the color customizer sample program provided in the
directory DECW$EXAMPLES to control DECwindows Mail colors, the
DECwindows Mail color customization dialog boxes used to modify those
colors may not reflect the correct current color values. This is normal
behavior; use the color customizer instead of the DECwindows Mail color
customization dialog boxes to change these values. Alternatively, exit
from the color customizer and restart DECwindows Mail. See Section 1.7
for more information about the color customizer.
1.9.12 DECwindows Motif Window Manager
This section contains information about the DECwindows Motif Window
Manager.
1.9.12.1 Using the Color Customizer with DECwindows Motif Window Manager
V1.2
If you are using the color customizer provided in the DECW$EXAMPLES
directory to control Motif Window Manager colors, the Motif Window
Manager customization dialog boxes used to modify those colors may not
reflect the correct current color values. This is normal behavior; use
the color customizer instead of the Motif Window Manager color
customization dialog boxes to change these values. Alternatively, exit
the color customizer and then restart Motif Window Manager. See
Section 1.7 for more information about the color customizer.
1.9.12.2 Configuration File
V1.0
The configuration file DECW$MWM_RC.DAT defines how the Window Manager uses the function keys. Most of the accelerators use the form Alt key (or Compose Character key) and function key, for example Alt+F7.
If any application needs to use these keys, you must either comment them out by placing an exclamation point (!) at the beginning of the line, or create new keyboard bindings. Then change Mwm*keyBindings:DefaultKeyBindings in the MWM resource file to point to the new bindings.
With the Motif binding, you can no longer use the Alt+spacebar or the Compose Character+spacebar to bring up the Window menu because it interferes with Compose Character sequences in DECterm. Use Shift+F11 to bring up the Window menu.
To reenable Alt+space, select the appropriate option in the Workspace
Options dialog box and apply the current settings. You can also remove
the comment for the default button bindings for Alt+space in the
DECW$MWM_RC.DAT file.
1.9.12.3 DECwindows XUI Applications
V1.0
The resource Mwm*useDECMode allows previous versions of DECwindows XUI
applications to behave correctly with the Motif Window Manager. In
particular, this resource is used to control focus, window placement,
multiline icons, and the window's initial state (normal or minimized).
1.9.12.4 Restarting Motif Window Manager
V1.0
The file SYS$MANAGER:DECW$MWM.COM is used for information on how to
restart the Window Manager. By default, it is always restarted on all
the screens that are available. However, if you are not starting the
Window Manager from the Session Manager, then the Window Manager might
not have been initially started on all the available screens. You can
modify this file to change the way the window is restarted for your
system.
1.9.13 Motif Window Manager---Known Problems
This section contains information about known problems with the Motif
Window Manager.
1.9.13.1 Customizing Color-Related Resources for Monochrome Monitors
V1.0
The Motif Window Manager does not support full customization of color-related resources for monochrome monitors in the Options dialog box. In order to change the colors, you might need to modify the pixmap resources by directly editing the DECW$MWM_BW.DAT resource file. For example, to change the color of the active window's title background, you must change the Mwm*activeBackgroundPixmap resource. Some values include 25_foreground, 50_foreground, 75_foreground, and unspecified pixmap.
In addition, by default, the title text is created with a white
background. To use the same color as the rest of the title, set the
Mwm*cleanText resource to FALSE.
1.9.13.2 Moving the Icon Box Off Screen
V1.0
If you move the icon box to the edge of the screen and then resize it
using the keyboard, you can move it off the screen. To retrieve the
icon box, press Alt+Tab until you reach that window and then press
Shift Escape (F11) to bring up the Window menu for that window. You can
then move the window back onto the screen.
1.9.13.3 Multihead Systems---Customizing Colors
V1.0
If you have a multihead system with different monitor types (color,
monochrome, or gray-scale), you can customize the colors only by using
the Options dialog box on the monitors that match the type of your main
monitor (screen 0). To customize the other monitors, you must either
log in to a system with that monitor type or directly edit the resource
files.
1.9.13.4 Multiline Icon Title Not Centered
V1.0
The Window Manager does not center all the lines of a multiline icon
title.
1.9.14 Notepad
This section contains information about the Notepad application.
1.9.14.1 Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit
V1.2--3
The Notepad application is linked with the OSF/Motif Release 1.1.3 Toolkit. Notepad is not modified to link with the OSF/Motif Release 1.2.3 Toolkit, which is provided with the DECwindows Motif Version 1.2-5 for OpenVMS product. The following restrictions apply:
This section contains information about the Paint application.
1.9.15.1 Private Colormaps
V1.1
If your workstation does not have sufficient colormap entries to view
or edit a color image, Paint creates a private colormap. When this
happens, the Paint image retains its colors, but the colors on the rest
of the workstation are modified. To restore the colors to their
original values, give another window input focus by clicking on it.
1.9.15.2 Enhancing the Performance of Some Paint Operations
V1.0
On GPX systems, Paint might appear slow even when performing basic operations such as drawing a brush stroke. This is because the pixmap is being swapped into the pixmap memory in order to paint the object. If Paint performance is slow, click on the Pencil tool and draw a point in the image area. This should improve performance following the initial Pencil click.
When editing images (especially color images), you can resize the image
area using the Picture Size... entry from the Options menu. Resize to
the least possible image area to significantly reduce the amount of
required pixmap memory.
1.9.16 Print Screen
This section contains information about the Print Screen application.
1.9.16.1 Print Screen---PostScript Output Problem
V1.2--5
When using the Print Screen application to produce PostScript output on some printers, part of the output may be lost. Usually, the upper and left portion is missing when printing in landscape mode and the lower and left portion is missing when printing in portrait mode. This problem is caused by differences between PostScript printers. To correct this problem, DECwindows Motif Version 1.2-5 for OpenVMS adds support for four new resources which can be specified in DECW$PRINTSCREEN.DAT:
PrintScreen.plxtranslate PrintScreen.plytranslate PrintScreen.plxscale PrintScreen.plyscale |
These resources control the size and position of the PostScript image on the page. The plxtranslate and plytranslate resources control the x and y offsets of the image in inches from the origin. The plxscale and plyscale resources are an x and y scale factor to allow the entire image to be displayed on the page after the origin is moved.
| Previous | Next | Contents | Index |