Common Functions
10 - 3
The String Editor
The
String Editor
is used to
name or rename test cards, tests and templates as
well as to fill out the Comment card.
Every time such an operation becomes necessary, the
String Editor
starts
automatically.
The number of available characters to choose from depends on the
String
Editor
’s use. If, for example, a user-defined comment is to be entered in the
Comment card, the number of available characters is bigger as if a test is to be
renamed. This difference are special characters such as !, ?, _, [ ], etc.
Important special characters:
↵
carriage return (line feed)
tab (special function in Form Editor mode; refer to page 8-34).
When started from Test Card View, Test Procedure Overview or File
Operations, the
String Editor
’s respective entry field shows a default name.
To accept the default name, press the menu key O K or S
A V E
.
To change the default name, and to enter a name of your choice
– delete the default name by repeatedly pressing the backspace key
– enter the new test or folder name by consecutively selecting the characters
of your choice from the "on-screen keyboard" with the U
P
/ D
O W N
keys or
by navigating to it with the handwheel
– acknowledge every selected character by pressing the handwheel or
E
N T E R
Use the
String Editor’s
arrow buttons to move the cursor to the position of your
choice. These buttons are only available if the focus (
⇒
Glossary) is on the
character selection.
On the Comment Card, pressing C
A R R I A G E
R
E T U R N
starts a new line.
Otherwise, C
A R R I A G E
R
E T U R N
is disabled.
Once the new name is entered, press the context-dependent menu key O K or
S
A V E
- depending on the mode - to exit the
String Editor
.
Pressing C
A N C E L
closes the
String Editor
discarding all changes.
Summary of Contents for CPC 100
Page 12: ...CPC 100 V1 41 x...
Page 28: ...CPC 100 V1 41 1 16...
Page 90: ...CPC 100 V1 41 3 14...
Page 194: ...CPC 100 V1 41 6 30...
Page 250: ...CPC 100 V1 41 8 32 Figure 24 Settings of Amplifier test card for this example use case...
Page 258: ...CPC 100 V1 41 9 4...
Page 264: ...CPC 100 V1 41 10 6...
Page 282: ...CPC 100 V1 41 12 10 Figure 9 Saving tests with the CPC Editor...
Page 284: ...CPC 100 V1 41 12 12...
Page 312: ...CPC 100 V1 41 14 12...
Page 316: ...CPC 100 V1 41 15 4...
Page 350: ...CPC 100 V1 41 16 34...
Page 372: ...OMICRON Contact Addresses 22...