Bug report in 0.84:
I have noticed that the u_vdata field gets munged when using
fl_set_browser_dblclick_callback(). When the actual callback gets called,
the object data passed in the set routine *does* get sent, but the
u_vdata, and (!!) u_ldata variables are either nulled or set to 0.
Other callbacks work (like the object callback), but the browser
double-click callback is hosed. Any ideas for a work-around?
-- Begin example --
serverlist_form->ListServers->u_vdata = (void*) this;
fl_set_browser_dblclick_callback(serverlist_form->ListServers,
ServerListDCallback, 0);
static void serverlist::ServerListDCallback(FL_OBJECT* ob, long)
{
if (((serverlist*) ob->u_vdata) == NULL)
cerr << "Object void data is NULL!\n";
int line = fl_get_browser(((serverlist*)
ob->u_vdata)->serverlist_form->ListServers);
}
-- End example --
And the ending result is:
-- Program run --
Object void data is NULL!
Segmentation fault.
-- End program run --
On standard objects, callbacks work fine. Something happened in the
browser. :/
Anyone else experience this?
----------------------------------------------------------------------
Ken T. Hollis || Autobahn Sys Admin || Freeware/GPL Hacker
khollis@northwest.com || Webmaster/Hacker || Linux Net Junkie
----------------------------------------------------------------------
"640K [RAM] ought to be enough for anybody" -- Bill Gates 1981
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html