You can set the contents of fields, etc. but you shouldn't actually draw.
For example, I have a utility routine to set the contents of a field that
takes a boolean redraw parameter (if the redraw is true, it calls
FldDrawField). I pass a redraw of false if calling from an init routine, but
true everywhere else
Neil
> Hmmm... I guess I've been living in some far-off fantasy world, but I
> haven't heard about this "drawing *after* calling FrmDrawForm" requirement
> before. My applications usually have an "Init" function called from
> frmOpenEvent in the form event handler that sets up the content of tables,
> fields, or whatever and finish with FrmDrawForm(). Is this no longer
> recommended? What should I be doing?
>
> --john
>
>>>3. The behavior of the FrmDrawForm API has been changed, in a specific
>>>way that is likely to cosmetically break some applications. Is this an
>>>intended change for 3.3?
>>
>>Sigh, this again. Well, it still indicates incorrect behavior in your app
>>- you should do your drawing *after* calling FrmDrawForm, because it is
>>correct for it to clear its content the first time it is coming up. But
>>this code has been taken out, again, as it happens. Consider this a
>>temporary reprieve, or as strike 2... (as in, 3 strikes and you're out!)
>
> ----------- Software for the Connected Lifestyle ------------
> John Powers Poohbah Industries
> The Grand Poohbah http://www.poohbah.com
> ==============================================================
>
>
>
>
