imacarthur wrote:
> I think Greg often renders Japanese text in his applications, and if
> I recall correctly, he does not use XFT in his builds? If so, that
> would tend to indicate that it *can* work...
In my case I was using fltk-1.1.6-utf8 when I had XFT off.
Now, with 1.3.x, I'm leaving XFT enabled because that's
the default.
I have not heard anything about crashes from Fl_Input with
1.3.x + XFT on linux, but I haven't gone into beta testing
yet.. I'm still in alpha.
It'd be cool if the OP could enable FLTK debugging, and pass
us a gdb calling stack. Assuming FLTK and your app are compiled
with debugging enabled (-g), should just be a matter of running
your app under GDB, eg:
gdb ./yourapp <-- starts gdb running your app
run <-- once gdb starts, type 'run' (followed by any
command line args your app needs)
..then when you click on an Fl_Input to get the program to
crash, the gdb prompt will return, at which point you can
print out the calling stack with eg:
where
..this will tell us where the crash happened.
For more info on debugging with gdb, I have some info here:
http://seriss.com/cgi-bin/erco/view-cheat.cgi#GDB
..and also google surely has lots of info too.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
