RE: XForms: another thing...

Danny G. Holstein (danny@holstein.tritonetd.com)
Thu, 17 Sep 1998 08:19:34 -0400 (EDT)

# To subscribers of the xforms list from "Danny G. Holstein" <danny@holstein.tritonetd.com> :

On 17-Sep-98 AMIT BHATNAGAR wrote:
># To subscribers of the xforms list from AMIT BHATNAGAR <amit@cs.dal.ca> :
>
>
>I was looking at my code for something else that would cause my crazy
>memory error.. and I noticed something: Why is it necessary(?) to call
>fl_create_form_xx() everytime you want to display a form after it has been
>hidden with fl_hide_form? If you don't call fl_crete_form_xx before you
>fl_show the form I get:
>
Whoa! That's your problem!
>
>Because my program is nothing but filling in formartion and going back and
>forth between forms.. is having to always call fl_create_form_xx good
>practice? Or is there nothing else I can do?
>
>also, If a form is just being hidden, why can't it 'remember' its
>contents. For example if I fl_hide_form; and then show it again, the items
>on the form are gone (items in like a browser or a input boxes), and I
>have to put the information back into the input fields by fl_set_input etc
>etc. (and an fl_free_form hasn't been issued).
>
You should have a call to fl_show_form(...). It makes perfect sense that malloc
would puke when you create the same form over and over again. When you use
fl_hide_form you need to use fl_show_form to bring it back, if you're going to
use fl_create_form you need to fl_free_form on that object before you create it
with the same name.

...Dan
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/