Janus wrote:
> let me know if you need any more information
Two things come to mind that you should check:
Are your tooltips static strings, eg:
tooltip("Some static string");
..or are they dynamic strings, eg:
std::string some_str;
:
tooltip(some_str.c_str());
char s[80];
sprintf(s, "This is tooltip %d", count);
:
tooltip(s);
If dynamic, make sure the string remains allocated for
the duration of your widget's lifetime, as FLTK doesn't
make a copy; it uses your pointer throughout the application.
If they're static and its still crapping out, then it might
be a bug somewhere.
Be sure if you recently switched to 1.3 that your #include's
aren't including files from a different version, eg. make sure
/usr/include/FL doesn't point to the 1.1.10 version while linking
against 1.3.x libs.
Also: dig deeper in the debugger to find the string of the tooltip
in question. If you link against the debug version of FLTK, you'll
be able to see what the string's value is. (eg. in gdb with
'up' and 'down' and 'print')
In this case it sounds like the string became NULL (invalid parameter
not satisfying: aString != nil)
which might mean a string went out of scope, or is pointing to random
memory. Either could be caused by the above two items.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
