[Uim] uim-pref-qt

[YAMAMOTO Kengo / YamaKen]

At Mon, 31 Jul 2006 17:40:03 +0900,
ek.kato at gmail.com wrote:
> 
> On 7/31/06, YAMAMOTO Kengo / YamaKen <yamaken at bp.iij4u.or.jp> wrote:
> > > So I leave uim-pref-qt unchanged at the moment.   YamaKen, if you know
> > > how to bypass IM context in some specific widgets, please let me know.
> >
> > Although I don't know about latest implementation and
> > distribution-specific fixes of the immodule patch,
> > QWidget::setInputMethodEnabled() is suitable for such purpose if
> > the behavior around it is not changed since last I touched.
> 
> Thanks for the information.  I think inputMethodEnabled value in the
> key capture widget is already set false.  But current qt-immodule
> patch seems to create a input context regardless of the value.
> Fedora's patch contains a following block, and it fixed the problem.
> 
> @@ -2754,10 +2753,8 @@
>  */
>   void QWidget::createInputContext()
>  {
> -#if !defined(QT_NO_IM_EXTENSIONS)
>      if( !isInputMethodEnabled() || QApplication::closingDown() )
>         return;
> -#endif
> 
>      QWidget *icWidget = icHolderWidget();
>   #ifndef QT_NO_IM

In my last release of the immodule patch, any widgets are
supposed to bypass input context filtering regardless of its
input context existence, by the fragment below.

QApplication::x11ProcessEvent( XEvent* event )
...
#ifndef QT_NO_IM
    if( keywidget && keywidget->isInputMethodEnabled() && keywidget->isEnabled() ) {


If the fragment is still existing untouched in the function, I
have no idea about what is happening on it. And I'm sorry of my
leaving from the immodule development. I have no time to brush
up it.

------------------------------------------------
YAMAMOTO Kengo / YamaKen  yamaken at bp.iij4u.or.jp
FAMILY   Given / Nick