> An interesting consequence of a typo. When the second
> object is cut, the tabfolder received an FL_FREEMEM
> event, instead of freeing the memory, it draws
> the tabfolder (can anyone guess what the typo is). The window the
> tabfolder appears in is somewhat random.
Sounds to me as if the
break;
was left off a case in a switch statement.
I love those -- they are responsible for enormous hair tearing.
Almost as good as inadvertently altering the value of a constant in a
FORTRAN program (anyone want to guess how to do *that* one?). Yes, I
do admit to having programmed, at one time in my insanely checkered
career, in FORTRAN.
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://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/