At 1:47 PM -0800 3/2/99, Uli Foerster wrote:
>Or is there some special reason for PalmComputing to discourage it's
>utilization in apps? Maybe discontinuation of availability in future OS
>versions or so?
In this case, I think you're probably right that using it is the best thing.
We discourage it's use for fields that are directly contained in forms
because the form needs to know who's got the focus. If you use
FldGrabFocus for one of those fields, then the form will still think
there's no focus or that some other object has focus, and then later when
the focus changes the wrong thing will happen.
In this case we should probably add some API that sets the focus to a
particular row/column of the table *and* fixes the field thing if that
table slot contains a field.
For now it looks like you have to call FrmSetFocus to tell the form that
the table has the focus, then call TblGrabFocus to create the field and
update the edit indicator, then call FldGrabFocus to turn on the insertion
point.
Same goes for fields that are contained in objects other than forms. (Say
you create your own form-like thing.) You'll need to manage the focus
changing yourself in that case, so you will need FldGrabFocus.
--Bob
