fhools wrote:
> I think it might be just a Fl_Input problem because I can use Ctrl-C Ctrl-V
> to copy paste items in the fluid gui builder, so that app must be
> registering Ctrl-C/V correctly.
The results from test/keyboard would seem to indicate it might be
more than just Fl_Input, but I'm not sure.
> I get XCreateIC failed when I start up fltk 1.3 applications.
XCreateIC() is XIM / input method related, so it sounds
like some of the X input stuff isn't initializing properly..
surely worth investigating.
The "XCreateIC() failed" message is in the fl_init_xim() function
of src/Fl_x.cxx (just search for that msg).
The logic for the error is here:
if (!fl_xim_ic) {
Fl::warning("XCreateIC() failed\n");
XCloseIM(fl_xim_im);
[..]
..which means fl_xim_ic is NULL, in which case it seems
to shut down all the XIM stuff. For fl_xim_ic to be NULL,
it must be the XCreateIC() code in fl_new_ic():
either XCreateIC() is never called, or one of the calls
that is being made is failing.
It might help if you can determine which (if any) of the three
XCreateIC() calls in fl_new_ic() is being called at all, and if
so, which of the calls is the one being used and fails. From that
we can maybe determine the cause. It could be some of the logic
in fl_new_ic() needs tweaking.
A lot of guesswork on my part, but hopefully someone else
more knowledgeable about the X code can chime in.. I don't
know any of this stuff, just looking stuff up in the man pages.
When we print X errors, we should probably print the 'reason'
if possible. From what I can tell, XCreateIC() seems to have
some kind of error indicator (similar to errno?); under DIAGNOSTICS
in the man page, it seems to show possible error values, though I'm
not sure I know (or remember) how to get and print them.
_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs
