[immodule-qt] Why reconstruct the number of event's event type to one?

[Daisuke Kameda]

On Wednesday 02 March 2005 12:59, Daisuke Kameda wrote:
> On Wednesday 23 February 2005 22:55, Lars Knoll wrote:
> > > The most important thing is that high extendibility
> > > and high readability are realizable. So, widget developer
> > > will be able to implement original processing of
> > > input method easily.
> >
> > The way I see this it won't be easy no matter what we do, as the widget
> > developer has to honour all the attributes for the preedit string. This
> > usually requires a lot more work than the commit or replace actions.
> >
> > I've talked about this with a few people here at Trolltech that are
> > involved with input methods (on embedded) and widget development. Noone
> > sees a big problem with having only one event.
> >
> > Fortunately there are very few people implementing their own input
> > widgets. All of KDE has 2-3 input widgets where they would need to
> > implement the event handling. Other projects are smaller and have at most
> > one input widget they write themselves, usually none at all.
>
> I see. But, I think it unclear to treat surrounding text
> and commit as the same thing.

I saw newest version.

I think that the implementation is not best solution.
But, I also think it is better solution because to use replace
committed string.

From now on, let's continue considering the best implementation. 

-- 
Daisuke Kameda <kaminmat at cc.rim.or.jp>