|
From: Araki K. <j00...@ip...> - 2001-12-13 00:49:32
|
Hi,
Subject: Re: [Mlterm-dev-en] Some problem of Big5 cut&paste and XIM(mlterm-cvs)
From: th...@li...
Message-ID: <200...@li...>
Date: Wed, 12 Dec 2001 23:33:22 +0800
> This should not happen for a standard X11R6 XIM client. I searched
> the whole source of mlterm, but I cannot find the function call of
> XRegisterIMInstantiateCallback() anywhere. This is the standard
> call of X11R6 to provide the ability of the XIM client to connect
> to the XIM server once it is available now.
Yes , but I don't use it now for the reason below.
> However, I note that since mlterm has the ability to choose/change
> the XIM server in *run time*. So I am not sure that if this is the
> reason that you don't want to use XRegisterIMInstantiateCallback()
> call in mlterm, or you just missed this point.
It is my decision not to use XRegisterIMInstantiateCallback() ,
this is because it is quite troublesome to process not only Open / Close
but Register / Unregister for switching multiple XIMs.
(that is , I cut corner:))
Of cource , it is possible , but I thought XRegisterIMInstantiateCallback()
may not be necessary , since even if XIM is killed and mlterm purges it ,
pressing XIM_OPEN keys after XIM is revived enables you to use it again anyway.
But the idea above is just my own decision , and if you all say
XRegisterIMInstantiateCallback() should be used and is necessary ,
I'll do it from now and wait for a while , please.
--
kiken
j00...@ip...
|