Typographical conventions used in this manual are outlined in the following table.

Example of ConventionDescription
SYSPROCSTable, file, and directory names; paths; as well as OpenInsight Properties, Events, and messages appear in all capital letters, in this typeface. Row, column, and table names also appear in all capital letters.

Note: Properties and Events must be typed in all capitals in order to be recognized by Presentation Server.

InitDir, OConv, Dialog_BoxWords in this typeface with the initial letter capitalized indicate an OpenInsight command (other than a Property or an Event), such as an operator, statement, function, subroutine, or declaration.
If C = " " Then Go 3 |

Else Go 5

Syntax and code examples appear in this font.
variablenameWords in lower case and italic type in syntax and code examples represent placeholders for information you supply, such as parameters.
escapeSmall capital letters indicate the names of keys, and key combinations.
ctrl+alt+delThe plus sign between keys indicates that you press all keys simultaneously.
[Compile]Optional commands and parameters in syntax are expressed in this manual using [ ] (square brackets). This usage differs from the Brackets operator, which is described in the “Brackets operator” topic in Chapter 2: BASIC+ Language Reference.
Then | ElseIn syntax, the vertical bar separates two mutually exclusive items. You must choose one.
dialogname = Create_Dialog |

(dialogID, | parentID, | mode, | initparam)

In code samples, the vertical bar tells the compiler that the following line is an extension of the current line.
* { characters }

! { characters }

REM { characters }

Single-line comments are indicated with the asterisk, exclamation point, or REM.
/* { characters } */Multi-line comments are blocked with the /* and */. It is not necessary to block each line of a multi-line comment.

Note: Notes draw your attention to information that may not be inherently obvious, but which is important to correct use.

  • No labels