Steve Patt wrote:
> I tried embedding the nextFieldChr in the character string
> to be pasted, with the idea that it would paste the first set of
> characters in the active field, then the nextFieldChr would skip to
> the next field, the next bunch of characters would go in the next
That won't work. Applications must handle nextFieldChr and prevFieldChr
themselves, when entered by the user, to explicitly move the focus
around. (Note to self: need to implement this... :-) In fact you
probably won't even find 'nextFieldChr' at all in the OS source code for
forms and fields.
Also, how would the OS even know which is the logical "next" field on
the form? By position on screen? By increasing ID number? It would be
nice, but presently there is no 'tab order' you can define in
Constructor, such as you can in Windows dialog resources.
-slj-
