> > switch (event)
> > {
> > case FL_DRAW: /* Redraw Object */
> > fl_freeze_form(test_form->test);
> /* fl_deactivate_form(test_form->test);*/
>
> Yeap, this is where things go wrong. When you receive
> FL_DRAW event, many of the book-keeping stuff has been
> taken care of by the event dispatcher.
> All you need to do (and it is assumed so) is draw. Any other
> high-level routines (freeze_form is one of them,
> fl_set_object_label, color, lalign font are others) would cause
> problems ( e.g., fl_set_object_color would cause infinate recursion).
>
I really believe that fl_freeze_form has no place here. All i wanted to do
is to stop form from getting mouse clicks (events) while i was doing
intense drawing. I have used fl_deactivate_form in the same place with no
success (In my original app, fl_deactivate_form simply did nothing, in the
test program i sent yesterday, if you dont use fl_freeze.. and you use
fl_deactivate_form, with the first mouse click, an X error occurs)
So if i couldn't stop getting events, at least to request to stop drawing
objects until finished...
It is also very reasonable, while doing intense drawing to turn the
cursor to a watch or something showing delay. If i try to change the cursor
with fl_set_cursor, again an X error occurs.. How can i manage this????
gp
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html