> > Are you doing anything in the Free object handler that manipulates any
> > other object? This tends to confuse XForms's internal bookkeeping and
> > will cause symptoms similar to those you describe.
> >
> > If you need to manipulate some other object, then do it in a
> > callback rather than in the handler. You can return a non-zero value
> > from the object handler to trigger the callback.
> >
>
> Yes, that fixed it! I *was* doing some stuff with other objects in the
> handler which I've moved to the callback and now everything looks fine.
Great.
TC, I think these things need to be documented a little better in the
manual. The manual should make it explicitly clear that manipulation
of other objects from a Free object or user defined object is a Bad
Thing. Also, I'm not sure that the expected return value from an
object handler (0 for no callback, non-zero for a callback) is
documented anywhere -- at least I couldn't find it last night when I
was trying to research this question. In fact, I'm not sure how I
even knew it, myself -- must be those darn telepathic implants... :-)
spl
_________________________________________________
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://bloch.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/