[immodule-qt] [PATCH] Surrounding text

Anuradha Ratnaweera gnu.slash.linux at gmail.com
Wed Oct 6 08:13:02 EEST 2004


On Tue, 28 Sep 2004 00:28:41 +0900, Daisuke Kameda
<kaminmat at cc.rim.or.jp> wrote:
> On Friday 24 September 2004 17:47, Anuradha Ratnaweera wrote:
>
> > Thanks.  What's the neat way add it only if qt+im is compiled with
> > binary incompatibility enabled?
> 
> I have considered. Probably, the best solution is that we implement
> QWidget::imGetSurrounding() and QWidget::imDeleteSurrounding()
> like QWidget::icHolderWidget().
> 
> These are set to virtual when QT_NO_IM_EXTENSIONS is defined
> (configure option is -inputmethod-ext). And these functions of QLineEdit
> and QTextEdit are made to be compiled only in this case.
> 
> What do you think about this solution?

Need a bit of clarification on this. (please be kind enough to correct
me if I say something silly here, because I am very poor at C++ and
OOP in general :-)).

As the im{Get,Delete}Surrounding() of the actual widgets (QLineEdit
and QTextEdit) are called only if they are virtual in QWidget, even
with the above solution, they will _work_ only if -inputmethod-ext is
specified.  Is it the same for icHolderWidget()?  If yes, what's the
reason to do it?  Is it to make sure that the im modules using these
functions compile whether -inputmethod-ext is specified or not?

If the answer to the last question is yes, I will send a new patch.  I
have almost done it, but didn't want to post until I get this bit
clarified.

Thanks in advance.

        Anuradha

-- 

http://www.linux.lk/~anuradha/
http://www.gnu.org/philosophy/no-word-attachments.html



More information about the immodule-qt mailing list