--- a/EditField.st	Wed Apr 23 16:20:00 2003 +0200
+++ b/EditField.st	Thu Apr 24 14:59:19 2003 +0200
@@ -54,45 +54,45 @@
     are passive; i.e. into which text can be entered and the value (string)
     is extracted actively by someone else.
 
-  accepting:
-    The opposite way to use editFields is to connect them to a model
-    and let the field notify changes to it.
-    This notification is called ``accepting''.
-    Unless accepted, the models value is not updated from the editFields contents
-    this default is the normal operation and way things should work, since most
-    uses of editFields are not interested in every individual change
-    (i.e. getting each keyStroke when a long number is entered).
-    The default behavior is to ``accept'' when either return or a cursorUp/Down
-    key is pressed in a field.
-    However, the field can setup to accept/not accept on leave, on return
-    or on each individual key input.
-    See the methods #acceptOnLeave: / #acceptOnReturn: / #immediateAccept.
-
-    In addition, the set of keys which are considered ``leaveKeys'' can be
-    specified by #leaveKeys: (in case you need keys other than Return, CursorUp/Down).
-
-  models value vs. field contents:
-    Although the field internally keeps its contents as some string object,
-    the application may prefer to think of numbers, floats, yes/no values etc.
-    To support this, a converter may defined, which is responsible for conversion of
-    strings to/from the models domain value.
-    If present (i.e. nonNil), the converter is asked to convert a string to the models
-    domain with #readValueFrom:aString and vice versa, a value to a string by #printStringFor:.
-    The PrintConverter class already provides a number of standard conversions, see the examples.
-    To access a converted value directly (i.e. not via the model), use #editValue.
-
-  grouping:
-    Individual fields do not know about being included in a group. This must be arranged on the
-    outside, by placing multiple fields into an EnterFieldGroup.
-    This groupObject keeps a reference to one active field, and forwards input from any other
-    field to the active one. Also have a look at the examples for this.
-
-  input completion:
-    To support input completion (i.e. filename completion, classname completion etc.),
-    a completionBlock can be defined which (if non-nil) is evaluated when the completion-key
-    is pressed and its value is taken as the new field-contents. 
-    The physical completion-key is the Tab key (this one cannot be defined by
-    the keyboardTranslation mechanism, since that would disable the Tab-key on regular text views.
+    accepting:
+      The opposite way to use editFields is to connect them to a model
+      and let the field notify changes to it.
+      This notification is called ``accepting''.
+      Unless accepted, the models value is not updated from the editFields contents
+      this default is the normal operation and way things should work, since most
+      uses of editFields are not interested in every individual change
+      (i.e. getting each keyStroke when a long number is entered).
+      The default behavior is to ``accept'' when either return or a cursorUp/Down
+      key is pressed in a field.
+      However, the field can setup to accept/not accept on leave, on return
+      or on each individual key input.
+      See the methods #acceptOnLeave: / #acceptOnReturn: / #immediateAccept.
+
+      In addition, the set of keys which are considered ``leaveKeys'' can be
+      specified by #leaveKeys: (in case you need keys other than Return, CursorUp/Down).
+
+    models value vs. field contents:
+      Although the field internally keeps its contents as some string object,
+      the application may prefer to think of numbers, floats, yes/no values etc.
+      To support this, a converter may defined, which is responsible for conversion of
+      strings to/from the models domain value.
+      If present (i.e. nonNil), the converter is asked to convert a string to the models
+      domain with #readValueFrom:aString and vice versa, a value to a string by #printStringFor:.
+      The PrintConverter class already provides a number of standard conversions, see the examples.
+      To access a converted value directly (i.e. not via the model), use #editValue.
+
+    grouping:
+      Individual fields do not know about being included in a group. This must be arranged on the
+      outside, by placing multiple fields into an EnterFieldGroup.
+      This groupObject keeps a reference to one active field, and forwards input from any other
+      field to the active one. Also have a look at the examples for this.
+
+    input completion:
+      To support input completion (i.e. filename completion, classname completion etc.),
+      a completionBlock can be defined which (if non-nil) is evaluated when the completion-key
+      is pressed and its value is taken as the new field-contents. 
+      The physical completion-key is the Tab key (this one cannot be defined by
+      the keyboardTranslation mechanism, since that would disable the Tab-key on regular text views.
 
 
 
@@ -2129,5 +2129,5 @@
 !EditField class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libwidg/EditField.st,v 1.165 2003-03-20 01:22:30 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libwidg/EditField.st,v 1.166 2003-04-24 12:59:19 cg Exp $'
 ! !