> You said that the name of the button was the same as the callback ? Well
> then the compiler should not compile the program but if it did it is
> possible that button2 is not a FL_OBJECT * but an address of the callback
> ! This would explain the compiler message and the coredump during run
> time. ...
Ah. I should have seen that the first go around on this. That's
*exactly* the problem. Blame it on whatever stomach bug I happened to
pick up that's laid me low the past couple of days. :-(
> ... Try being very specific and define different names for objects and
> callbacks (like button3 for the object and button3_cb for the callback).
Although this is good practice (I use the same convention, so it
*must* be good practice :-) ), it isn't absolutely necesary since the
callback name and the object name live in two separate name spaces and
never the twain shall meet.
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/