Re: XIM application frozen on gtk+1.3.*

[tajima <hidetoshi tajima eng sun com>]

>> >It should be noted that the way that GtkIMContextXIM handles
>> >interaction with Xlib is definitely not fully compliant with the way
>> >XIM is supposed to, and while kinput2 seems to work reasonably well,
>> >other input methods probably will need some changes to the 
>> >way the module works.
>> 
>> Can we extend IM framework and allow XIM module to support
>> Over-the-spot and Root-window inputstyle as well? Root-window style
>> is relatively easy and Over-the-spot oughts to work *to some extent*
>> if gtk window can set spot-location.
>
>Root-window should work now. I'm not sure I want to add over-the-spot
>handling. I think it complicates the interface more than it is worth.

Well, I have two reasons for wants of spot location. It is often the case
that input methods use lookup choice windows to select a choice among
candidates, and these windows are typically poped up near the insertion
point, so that users can keep his eyes on the point.

Another reason is that there are still many XIM modules which don't support
on-the-spot. Fallback to Root-Window mode can be a workaround, but
not all user will like it.

>> Then, most of existing input methods would work with the XIM in
>> the new IM Framework, almost equivalently to the GDK's XIM.
>
>Well, the problem I think we have now is not that input methods
>require over-the-spot handling, but that input methods try to do some
>stuff that doesn't work well with the way gtkimcontextxim handles
>events.

Sure, let's get back to the original frozen problem, but I'd like to raise 
over-the-spot as a separate problem, too.

thanks,
-toshi