DOMAIN/Dialogue Release Document
Version 1.0
Software Release 9.0
Part No. 005275
Revision 00
These notes apply to DOMAIN/Dialogue
1.0, which runs with SR9.0 or a later
software release (DOMAIN/Dialogue
does not run on earlier versions of
DOMAIN system software.) These notes
explain installation procedures,
changes to documentation, and
software bugs and bug fixes.
APOLLO COMPUTER INC.
330 Billerica Road
Chelmsford, Massachusetts 01824
c 1985 Apollo Computer Inc.
All rights reserved.
Printed in U.S.A.
Print date: July, 1985
This document was formatted using the FMT tool distributed with the DOMAIN
computer system.
APOLLO and DOMAIN are registered trademarks of Apollo Computer Inc.
AEGIS, DOMAIN/IX, DOMAIN/Dialogue, D3M, DPSS, DGR, GMR, GPR, and DSEE are
trademarks of Apollo Computer Inc.
Apollo Computer Inc. reserves the right to make changes in specifications and
other information contained in this publication without prior notice, and the
reader should, in all cases, consult Apollo Computer Inc. to determine
whether any such changes have been made.
THE TERMS AND CONDITIONS GOVERNING THE SALE OF APOLLO COMPUTER INC. HARDWARE
PRODUCTS AND THE LICENSING OF APOLLO COMPUTER INC. SOFTWARE CONSIST SOLELY OF
THOSE SET FORTH IN THE WRITTEN CONTRACTS BETWEEN APOLLO COMPUTER INC. AND ITS
CUSTOMERS. NO REPRESENTATION OR OTHER AFFIRMATION OF FACT CONTAINED IN THIS
PUBLICATION, INCLUDING BUT NOT LIMITED TO STATEMENTS REGARDING CAPACITY,
RESPONSE-TIME PERFORMANCE, SUITABILITY FOR USE OR PERFORMANCE OF PRODUCTS
DESCRIBED HEREIN SHALL BE DEEMED TO BE A WARRANTY BY APOLLO COMPUTER INC. FOR
ANY PURPOSE, OR GIVE RISE TO ANY LIABILITY BY APOLLO COMPUTER INC.
WHATSOEVER.
IN NO EVENT SHALL APOLLO COMPUTER INC. BE LIABLE FOR ANY INCIDENTAL,
INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT
LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATING TO THIS PUBLICATION OR
THE INFORMATION CONTAINED IN IT, EVEN IF APOLLO COMPUTER INC. HAS BEEN
ADVISED, KNEW OR SHOULD HAVE KNOWN OF THE POSSIBILITY OF SUCH DAMAGES.
THE SOFTWARE PROGRAMS DESCRIBED IN THIS DOCUMENT ARE CONFIDENTIAL INFORMATION
AND PROPRIETARY PRODUCTS OF APOLLO COMPUTER INC. OR ITS LICENSORS.
Reader_Notice
Chapters 1 through 3 of this document reside on-line in the /doc directory.
Chapter 4 is only available in hard copy.
To print a copy of this document, use the PRF command with the -pr and -npag
options.
PRF <filepathname> -PR <printername> -NPAG
iii
Contents
Section Page
CHAPTER 1 OVERVIEW OF DOMAIN/DIALOGUE 1.0 . . . . . . . . . . . . . . 1-1
CHAPTER 2 INSTALLATION PROCEDURES . . . . . . . . . . . . . . . . . . 2-1
CHAPTER 3 CHANGES TO DOCUMENTATION . . . . . . . . . . . . . . . . . 3-1
CHAPTER 4 BUGS AND BUG FIXES . . . . . . . . . . . . . . . . . . . . 4-1
(Chapter 4 is only available in hard copy)
Contents iv
CHAPTER 1
OVERVIEW OF DOMAIN/DIALOGUE 1.0
DOMAIN /Dialogue Version 1.0 consists of the DOMAIN/Dialogue product, a tool
for creating user interfaces to application programs. It requires that the
standard SR9 DOMAIN System software already be installed.
You can only add DOMAIN/Dialogue software to a node or DOMAIN system server
that is running the SR9 version of the DOMAIN operating system. If a node is
not running SR9, follow the SR9 software update procedures. These procedures
are described in Chapter 2 of Standard_Software_Release_Document_--_Software
Release_9.0 (Order No. 005354, Revision 03).
1-1 Software Release 9.0
CHAPTER 2
INSTALLATION PROCEDURES
This chapter describes how to install SR9 optional software products. You
can add this software to a node or DOMAIN System server that is running the
SR9 version of the DOMAIN operating system. If a node is not running SR9,
follow the SR9 software update procedures. These procedures are described in
Chapter 2 of Standard__Software__Release__Document__--__Software__Release__9.0
(Order No. 005354 Revision 03).
Some SR9 optional products will also run on SR8 AEGIS. Refer to Chapter 1 of
these release notes or to the dependencies section in Chapter 1 of the
Standard Release Notes to find out if an optional product runs on SR8 AEGIS.
The software installation procedures assume that you do not have links to any
optional software objects except for possible links to the following:
CC /sys/help
CORE no expected links
DIALOGUE /sys/help
FORTRAN /sys/help
GPIO /sys/help
Pascal /sys/help
TCP/IP /sys/help /sys/tcp /com/net
If you have links to any other system software, delete the links before
starting the installation. Failure to delete the links may result in the
objects pointed to by the links being deleted.
This chapter describes a two-phase approach to installing optional software.
2.1 WHICH INSTALLATION PROCEDURE TO USE
There are two installation procedures. Determine which one to use before
going any further.
2-1 Software Release 9.0
2.1.1 Use the Installation Procedures for System Administrators
o Use this procedure if you are a system administrator creating a
source area and designating the source area's installation program
as a protected subsystem. For more information about protected
subsystems, see Administering__Your__DOMAIN__System. You can use
cartridge tape, magnetic tape, a floppy disk, or an existing source
area.
o Use this procedure if you are a user who has the rights to delete and
change your system directories and you want to maintain those rights.
System directories include /SYS, /COM, /DOC, /DOMAIN_EXAMPLES,
/BSCOM, and /LIB. Use the ACL command to learn your rights; ACL is
documented in the DOMAIN_System_Command_Reference.
o Note that if you are a system administrator creating a protected
subsystem, you can install the software from a source area or into a
target area that is not at the entry directory (/) level. (Of
course, if you do not install the software at the entry directory
level, the node will not boot off of the new software; it will boot
from the software at the entry directory level.) You can install
various optional software products into a source area and then use
this source area to selectively install optional products on the
nodes in the network.
For example, first create a directory //node/sr9_source_area. Then,
when installing from tape or floppy into this area, use
//node/sr9_source_area as the target volume name. To load from this
area onto other nodes, use //node/sr9_source_area as the source
name.
2.1.2 Installation Procedure for Users:
o Use this procedure if you are a user who does not have the rights to
delete and change your system directories. System directories
include /SYS, /COM, /DOC, /DOMAIN_EXAMPLES, /BSCOM, and /LIB. Use
the ACL command to learn your rights; ACL is documented in the
DOMAIN_System_Command_Reference.
o You can only use this procedure if your system administrator
establishes a source area and designates the installation program in
the source area as a protected subsystem. You can copy the optional
software from any release media, but you must use the INSTALL program
from the source area designated by your system administrator.
Software Release 9.0 2-2
2.2 CONVENTIONS AND TERMINOLOGY
The terms and conventions used in these procedures are as follows:
o "Work node" is the node with a keyboard and display that you are
using to enter the commands to do the software installation.
o "Target volume" is the Winchester disk or mass storage disk on which
you are installing new software. You do not have to install the new
software into the target volume's entry directory (e.g., you are
creating a source area in a subdirectory on the target volume).
NOTE: When you are installing software to update a diskless node,
the target volume is the partner node's disk.
o "Target node" is the node or DOMAIN Server Processor (DSP) on which
you are installing or updating (i.e., the node that contains the
target volume). If the target node has a keyboard and a display
(i.e., it is not a DSP), the work node and the target node can be the
same.
o "Source" You must choose the source for your new software. If you
are installing the software using the procedure in the system
administrator phase, the source for the new software can be floppy
disks, magnetic tape, cartridge tape, or another node in the
network. If you are installing the software using the procedure in
the user phase, the source for the INSTALL program is the INSTALL
program marked as a protected subsystem by your system administrator.
You can get the rest of the SR9 software from the distribution
media.
The "source volume" is a Winchester disk or mass storage disk that
has already been updated with the new software. A "source node" is a
node in the network that has already been updated with the new
software (i.e., the node that contains the source volume).
NOTE: Ensure that the source volume contains the appropriate
optional software for the target node.
o A "secure network" is a network with a registry of user accounts and
access control of system software; an "open network" does not contain
user accounts and access control of system software.
o Angle brackets ( < > ) enclose the name of a key on the keyboard.
2-3 Software Release 9.0
2.3 INSTALLATION PROCEDURES FOR SYSTEM ADMINISTRATORS
Use these procedures if you are a user who has rights to modify your system
directories, or if you are a system administrator establishing a protected
subsystem.
If you are a system administrator establishing a protected subsystem, then
create a directory which will contain the INSTALL directory and the optional
software before you begin to install software. In the install procedures, you
must give this directory's pathname when you are asked for the target_volume.
You must also give the same pathname when you are asked to name a source area
for the protected subsystem.
1) Log in to a work node either as a SYS_ADMIN or log in as yourself.
Start a Shell on the work node. (This can be the target node.)
2) If you are installing the optional software over the network, then
skip step 2. If you are using a tape cartridge, a magnetic tape, or a
floppy disk to install the optional software, then perform step 2.
a. Set your working directory to //target_volume:
$ WD //target_volume <RETURN>
b. Insert the media into the drive and enter the RBAK command
shown below. If you are using a tape cartridge, use the CT
option shown in the example. If you are using a magnetic
tape, use the M0 (Mzero) option instead of CT. If you are
using a floppy, use the F0 (Fzero) option instead of CT.
$ RBAK -DEV CT -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
$ RBAK -DEV M0 -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
$ RBAK -DEV F0 -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
c. Set your working directory to //target_volume/INSTALL:
$ WD //target_volume/INSTALL <RETURN>
3) If you are installing the software from a cartridge tape, a magnetic
tape or a floppy, then skip this step. If you are installing the
software over the network, then perform this step. Set your working
directory to //source/INSTALL.
Software Release 9.0 2-4
$ WD //source/INSTALL <RETURN>
4) Only perform this step if you are logged in as a system administrator
and you are creating a source area. Do not execute the step if you
are logged in as a user. Enter the following command to select a
source area to install the optional software in:
$ INIT_SOURCE
5) Execute the INSTALL Shell script and follow the prompts:
$ INSTALL <RETURN>
6) The program prompts you to enter an installation type. Enter OPT and
press <RETURN>.
Software Installation Types are:
STD -- Install SR9 standard software
RESTART -- Restart the software installation.
OPT -- Install optional software (i.e. Pascal, Fortran)
ACL -- Set ACLs for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
DOMAIN_IX -- Install the DOMAIN/IX software
Please Enter Installation Type:
7) The procedure then asks if you have adequate rights to modify system
directories. You must answer yes to this question.
You must have sufficient rights to modify system directories
on the target node for the installation procedure to
work properly.
You are logged in as:
person.project.organization.node_number node_name
Do you have adequate rights ?
Please enter response. (yes or no):
8) You are then prompted for the name of the target volume. Enter it
and press <RETURN>.
** SR9 Optional Software Installation **
2-5 Software Release 9.0
Please enter the name of the TARGET volume that the SR9 Optional
Software will be installed on. (e.g. '//UPDATE_ME'):
Enter TARGET Volume or type 'quit':
9) The procedure prompts you for the name of the source media. Enter it
and press <RETURN>.
Source MEDIA is one of:
CTAPE -- SR9 Release Cartridge Tape
FLOPPY -- SR9 Release Floppy Disk
MTAPE -- SR9 Release Magnetic Tape
NET -- A volume on the network with SR9 software
Enter Source Media or type 'quit':
10) If you have an optional INSTALL directory on your node, then the
prodedure asks if you want to update the optional INSTALL directory
on your node. If you do not have a copy of this directory on your
node, the procedure asks if you would like one.
Would you like to update your OPTIONAL INSTALL
directory on //target_node ?
Please enter YES or NO or QUIT:
You presently do not have a local copy of the optional INSTALLATION
procedures. Would you like an OPTIONAL INSTALL directory installed
locally on your //target_node?
11) Enter the name of the optional product that you want to install and
press <RETURN>.
Name Description Disk Blocks Needed
(Adding New Software)
CC C compiler 700
CORE Core library 500
DIALOGUE DOMAIN/Dialogue 1000
FTN FORTRAN Compiler 500
GPIO GPIO Software 950
PAS Pascal Compiler 550
TCP TCP/IP 900
Enter the name of a single optional software product you
would like to install.
Enter an optional software product name:
12) If you selected TCP, the procedure prompts you for the name of the
Software Release 9.0 2-6
GATEWAY node. Enter it and press <RETURN>.
Please enter the name of the HOST GATEWAY node.
(e.g. //GATEWAY)
Enter GATEWAY node name or type 'quit':
13) If you specified NET, the procedure prompts you for the source
volume. Enter the source volume and press <RETURN>.
Enter the name of the source volume from which to copy the
SR9 Optional Software (e.g., '//VIVALDI'):
Enter Source Volume or type 'quit':
14) The procedure verifies that you have adequate disk space.
PLEASE WAIT... CHECKING DISK SPACE
.
.
15) If you are using magnetic tape, cartridge tape, or floppy disks, the
procedure asks you to insert the media into the drive. Do so and
press <RETURN>.
16) The procedure installs the software. When it is finished, check the
transcript pad to verify that all the files were copied, then press
<RETURN>.
PLEASE WAIT... THE INSTALLATION IS IN PROGRESS
.
.
.
**** Please check the transcript pad to verify ****
**** that all files were copied. If all files ****
**** were copied then the installation succeeded.****
**** If all files were not copied then the ****
**** installation failed. ****
Press <RETURN> when ready:
17) Enter the proper option and press <RETURN>.
Options:
RERUN -- There was a problem with the installation.
Please check the transcript pad for errors.
Type RERUN if you wish to rerun the installation
2-7 Software Release 9.0
for the optional product.
FINISH -- You would like to finish the installation
session and return to the shell level.
CONTINUE -- Install additional optional software.
Enter an option:
18) If you selected FINISH and if there were no errors during the
installation, the procedure instructs you to shut down the target
node, reboot it, and run the optional cleanup procedure.
If there were no errors, please shut down [the target node],
reset and reboot //target node.
Log in and run the install/opt_cleanup.
To run the optional cleanup procedures, set your working
directory to the install tree you used for this installation.
Then enter opt_cleanup <RETURN>
19) Use the Display Manager SHUT command to shut down the target node.
<cmd> shut
20) After the SUCCESSFUL SHUTDOWN message and the ">" prompt appear,
reboot the node by typing the following at the prompt: RE <RETURN>
<RETURN> EX AEGIS.
> RE
> <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS.
21) Set your working directory to //source/INSTALL directory. Run the
cleanup procedure by typing the following command:
$ OPT_CLEANUP
You are finished with the installation.
Software Release 9.0 2-8
2.4 INSTALLATION PROCEDURES FOR USERS
1) Log in to a work node as yourself. Start a Shell on the work node.
2) Set your working directory to //source/INSTALL. The source area must
have been created by your system administrator. (The installation
procedures for users require that you use the INSTALL program
designated by your system administrator.)
$ WD //source/INSTALL <RETURN>
3) Execute the INSTALL Shell script and follow the prompts:
$ INSTALL <RETURN>
4) The program prompts you for an installation type. Enter OPT and press
<RETURN>.
Software Installation Types are:
STD -- Install SR9 standard software
RESTART -- Restart the software installation.
OPT -- Install optional software (ie. Pascal, Fortran)
ACL -- Set acl's for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
DOMAIN_IX -- Install the DOMAIN/IX software
Please Enter Installation Type:
5) The procedure asks if you have adequate rights to modify system
directories. You must answer no.
You must have sufficient rights to modify system directories
on the target node for the installation procedure to
work properly.
You are logged in as:
person.project.organization.node_number node_name
Do you have adequate rights ?
Please enter response. (yes or no):
6) The procedure prompts you for the name of the target volume. Enter it
and press <RETURN>.
2-9 Software Release 9.0
** SR9 Optional Software Installation **
Please enter the name of the TARGET volume that the SR9 Optional
Software will be installed on. (e.g. '//UPDATE_ME'):
Enter TARGET Volume or type 'quit':
7) Enter the type of the source media and press <RETURN>. (You can
choose any of these options.)
Source MEDIA is one of:
CTAPE -- SR9 Release Cartridge Tape
FLOPPY -- SR9 Release Floppy Disk
MTAPE -- SR9 Release Magnetic Tape
NET -- A volume on the network with SR9 software
Enter Source Media or type 'quit':
8) If you have an optional INSTALL directory on your node, then the
prodedure asks if you want to update the optional INSTALL directory
on your node. If you do not have a copy of this directory on your
node, the procedure asks if you would like one. Enter yes, no, or
quit.
Would you like to update your OPTIONAL INSTALL
directory on //target_node ?
Please enter YES or NO or QUIT:
You presently do not have a local copy of the optional INSTALLATION procedures.
Would you like an OPTIONAL INSTALL directory installed locally on your
//target_node?
9) Enter the name of the optional product that you want to install.
Name Description Disk Blocks Needed
(Adding New Software)
CC C compiler 700
CORE Core library 500
DIALOGUE DOMAIN/Dialogue 1000
FTN FORTRAN Compiler 500
GPIO GPIO Software 950
PAS Pascal Compiler 550
TCP TCP/IP 900
Enter the name of a single optional software product you
would like to install.
Enter an optional software product name:
Software Release 9.0 2-10
10) If you select TCP/IP, you are prompted to enter the name of the
GATEWAY node.
Please enter the name of the HOST GATEWAY node.
(e.g. //GATEWAY)
Enter GATEWAY node name or type 'quit':
11) The procedure then checks disk space. If there is enough space, the
install proceeds automatically. When it is finished, check the
transcript pad to verify that all the files were copied, then press
<RETURN>.
PLEASE WAIT... CHECKING DISK SPACE
.
.
12) If you are using magnetic tape, cartridge tape, or floppy disks, the
procedure asks you to insert the media into the drive. Do so and
press <RETURN>.
PLEASE WAIT... THE INSTALLATION IS IN PROGRESS
.
.
.
**** Please check the transcript pad to verify ****
**** that all files were copied. If all files ****
**** were copied then the installation succeeded. ****
**** If all files were not copied then the ****
**** installation failed. ****
Press <RETURN> after you have checked the transcript pad:
13) Enter the proper option and press <RETURN>.
You are finished with the optional product installation.
Options:
RERUN -- Rerun the installation with the same parameters.
CONTINUE -- Continue to install additional optional software.
FINISH -- Finish the installation session and return
to the shell level.
Enter an option:
2-11 Software Release 9.0
14) If you selected FINISH and if there were no errors during the
installation, the procedure instructs you to shut down the target
node, reboot it, and run the optional cleanup procedure.
If there were no errors, please shut down [the target node],
reset and reboot //target node.
Log in and run the install/opt_cleanup.
To run the optional cleanup procedures, set your working
directory to the install tree you used for this installation.
Then enter opt_cleanup <RETURN>
15) Use the Display Manager SHUT command to shut down the target node.
<cmd> shut
16) After the SUCCESSFUL SHUTDOWN message and the ">" prompt appear,
reboot the node by typing the following at the prompt: RE <RETURN>
<RETURN> EX AEGIS.
> RE
> <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS.
17) Set your working directory to //source/INSTALL directory. Run the
cleanup procedure by typing the following command:
$ OPT_CLEANUP
You are finished with the installation procedures.
Software Release 9.0 2-12
CHAPTER 3
CHANGES TO DOCUMENTATION
This chapter supplements the DOMAIN/Dialogue_User's_Guide (Order No. 004299,
Revision 00). It corrects documentation errors and explains features that
could not be documented when the manual went to press.
Initially, you might glance briefly through this chapter to identify sections
of the manual that have changed. If you wish, check off the sections in the
manual. As you read, the check marks serve as a reminder to consult these
notes for the most recent information.
Section_3.6_Using_GPR_and_GMR_with_DOMAIN/Dialogue
For graphics applications, you may want to enclose the DOMAIN/Dialogue
event-wait call within GPR routines for acquiring and releasing the display
as shown below and in Figure 3-6 of the manual:
unobs := gpr_$acquire_display (status) ;
dp_$event_wait (task, event, status) ;
gpr_$release_display (status) ;
While not absolutely necessary, doing so enhances program performance. If
the display is not acquired when DOMAIN/Dialogue is called, it will not be
acquired when DOMAIN/Dialogue gives control back to the application. Thus
DOMAIN/Dialogue must acquire and release the display with each call, and the
application must acquire and release the display each time it does GPR
output. Avoiding the overhead involved in continually acquiring and releasing
the display is particularly important when doing feedback in a GRAPHICS_AREA
technique based on locator input, for example, rubber banding.
Section_4.4_Using_and_Defining_Keys
DOMAIN/Dialogue provides a suggested set of key bindings that you can use.
The bindings are shown below and in Table 4-1, but they do not apply
automatically to window (or other) techniques as Section 4.4 states. If you
want the key definitions, include them in your .dps file according to the
instructions given later in this section. The reason for this change is to
give you the option of whether or not to use the bindings. If you choose to
use them, they save you the trouble of defining your own bindings. However,
they override Display Manager key definitions while the locator is within the
DOMAIN/Dialogue window. For example, if a user has a Display Manager key
3-1 Software Release 9.0
definition file that defines M1 (the leftmost mouse button) to pop windows,
he or she could not do so in the DOMAIN/Dialogue window if you used the
predefined bindings. This is because the bindings define M1 to perform the
"select" operation on techniques.
If you do not want to use all the predefined bindings, you can define your
own bindings in the window or other technique (Section 4.4 of the manual and
its following subsections tell you how). If you want to use the key bindings,
they exist in a file called /sys/ins/dialog_user.ins.dps. The file declares a
window technique template containing the definitions as follows:
std_window := WINDOW !TEMPLATE:
[CR] => <+ accept> ;
[BS] => <+ backspace> ;
[CHAR_DEL] => <+ char_del> ;
[HELP] => <* help> ;
[INS] => <+ insert_toggle> ;
[LINE_DEL] => <+ line_del> ;
[TAB] => <+ next_field> ;
[DOWN_BOX_ARROW] => <+ scroll_down> ;
[LFS] => <* scroll_down> ;
[LEFT_BOX_ARROW] => <+ scroll_left> ;
[L7S] => <* scroll_left> ;
[LEFT_BAR_ARROW] => <+ scroll_left_justify> ;
[L4S] => <* scroll_left_justify> ;
[LAS] => <+ scroll_left_unit> ;
[RIGHT_BOX_ARROW] => <+ scroll_right> ;
[L9S] => <* scroll_right> ;
[RIGHT_BAR_ARROW] => <+ scroll_right_justify> ;
[L6S] => <* scroll_right_justify> ;
[LCS] => <+ scroll_right_unit> ;
[UP_BOX_ARROW] => <+ scroll_up> ;
[LDS] => <* scroll_up> ;
[M1] => <* select> ;
END
To use the definitions, "include" the file in the user_interface portion of
the .dps file, and use "std_window" instead of "window" for the window
technique. An example is shown below:
Software Release 9.0 3-2
USER_INTERFACE name
%include "/sys/ins/dialog_user.ins.dps"
.
.
.
std_window:
contents = technique_name
end.
Manual Parts Affected: In Figure 4-5, DRAW's window technique should now be
shown as follows:
std_window:
help_file = "/domain_examples/dialog/draw.hlp"
contents = row_with_menus_and_graphics_area
end
In Appendix D, DRAW's description files (Sections D.2.1 and D.2.2) should
have the %include statement, and they should use "std_window" instead of
"window". The help file pathname should be
"/domain_examples/dialog/draw.hlp". Appendix D should also show
"dialog_user.ins.dps" as one of the files for DOMAIN/Dialogue.
Chapter_5,_DOMAIN/Dialogue_Task_Types
BOOL, ENUM, INT, REAL, SET, and STRING tasks have a new attribute called
"Changes_only", which can be set to true or false. The default value is
"true," which means that if the user reenters the current value of a task,
the application is not notified. If set to "false," then the application is
notified of new values, even if they are the same as the current value. The
attribute should be added to list of attributes in the descriptions of BOOL,
ENUM, INT, REAL, SET, and STRING tasks and to the description of task
attributes in Section 5.11.
Manual Parts Affected: In the Quick Reference Section, "Changes_only" should
be added to the chart labeled "Task Attributes and Their Default Values".
Section_5.7,_The_Null_Task
There is a new way to trigger the "comp" (completed) task event for NULL
tasks only. To do so, include an action statement similar to the one shown
below in a technique action list.
[F2] => <exit comp>
This feature lets you trigger the "comp" event for a NULL task without having
to define and use a techique. In this example, pressing F2 triggers the
3-3 Software Release 9.0
"comp" event in a NULL task called "exit". If the example statement were
placed in a window technique, the user could invoke the exit task anywhere
within the DOMAIN/Dialogue window simply by pressing F2 (assuming that the
definition is not overridden in another technique).
Although "comp" looks like a techique operation in the statement above (see
Section 4.4.1), it is not really so, since it causes something to happen to a
task. In actuality, "comp" is more like a task operation; however, it is the
only task operation DOMAIN/Dialogue supports.
Manual Parts Affected: In Section 5.7, "comp" should be noted in the
description of the NULL task as an operation that can be performed upon it
from any technique.
Chapater_7,_DOMAIN/Dialogue_Library_Routines
Seven new routines are available for applications that use GPR or GMR. The
routines enable and disable input and set cursor pattern and origin. The
routines and their parameters are shown below and are similar to their GPR
and GMR counterparts except that all of them start with "DP_$" and have an
additional parameter, "task_id". The routines were implemented so that
DOMAIN/Dialogue graphics applications can use them to affect the
GRAPHICS_AREA technique exclusively. Using the GPR or GMR versions would
affect input, cursor pattern, and cursor origin outside the GRAPHICS_AREA as
well.
For a description of the routines and their data types, consult Programming
with__DOMAIN__Graphics__Primitives, (Order No 005808, Revision 00) and
Programming__with__DOMAIN__2D__Graphics__Metafile__Resource (Order No. 005097,
Revision 00).
PROCEDURE dp_$gpr_enable_input (
IN task_id: dp_$task_id ;
IN event_type: gpr_$event_t ;
IN key_set: gpr_$keyset_t ;
OUT status: status_$t ) ; EXTERN;
PROCEDURE dp_$gpr_disable_input (
IN task_id: dp_$task_id ;
IN event_type: gpr_$event_t;
OUT status: status_$t ) ; EXTERN;
PROCEDURE dp_$gpr_set_cursor_pattern (
IN task_id: dp_$task_id ;
IN cursor: gpr_$bitmap_desc_t ;
OUT status: status_$t ) ; EXTERN ;
PROCEDURE dp_$gpr_set_cursor_origin (
IN task_id: dp_$task_id ;
IN origin: gpr_$position_t ;
OUT status: status_$t) ; EXTERN ;
Software Release 9.0 3-4
PROCEDURE dp_$gmr_input_enable (
IN task_id: dp_$task_id ;
IN event_type: gm_$event_t ;
IN key_set: gm_$keyset_t ;
OUT status: status_$t ) ; EXTERN;
PROCEDURE dp_$gmr_input_disable (
IN task_id: dp_$task_id ;
IN event_type: gm_$event_t;
OUT status: status_$t ) ; EXTERN;
PROCEDURE dp_$gmr_cursor_set_pattern (
IN task_id: dp_$task_id ;
IN style: gm_$cursor_style_t ;
IN size: gm_$point16_t ;
IN pattern: UNIV gm_$cursor_pattern_t ;
IN offset: gm_$point16_t ;
OUT status: status_$t ); EXTERN;
Manual Parts Affected:
Table 3-1 should list the seven new routines under the heading "GPR and GMR
Routines with DOMAIN/Dialogue counterparts." In the same table, the first two
groups of routines under the heading "GPR Routines not Supported by
DOMAIN/Dialogue" now have counterparts (except for
GPR_$SET_CURSOR_POSITION).
In Chapter 5, the descriptions of GMR and GPR tasks should show the new
routines supported by each task.
Appendix B should show the additional data types used by the routines. For
GPR, the data types are: "gpr_$event_t" and "gpr_$keyset_t". For GMR,
additional data types are "gm_$cursor_pattern_t", "gm_$cursor_style_t",
"gm_$event_t", "gm_$keyset_t", and "gm_$point16_t".
Appendix D should show the seven new routines in Dialog.ins.pas, the standard
Pascal insert file for DOMAIN/Dialogue (Section D.5.1).
In the Quick Reference Section, the chart for the DOMAIN/Dialogue Library
Routines should show the new routines.
Additional_Example_Programs
The directory /domain_examples contains several example programs in addition
to DRAW. The programs are in Pascal and are described below.
GMDRAW -- is an application similar to DRAW, but it is built on GMR
rather than GPR.
PRINT -- is a "null" application. Only the interface is provided in
order to demonstrate activating and deactivating task groups.
3-5 Software Release 9.0
NUMBERS -- is another null application, which suggests combinations of
DOMAIN/Dialogue techniques useful for numeric input.
DIGCLK -- is a simple clock application that demonstrates the use of
DP_$COND_EVENT_WAIT.
Software Release 9.0 3-6