Re: [E-devel] [PATCH] Clear the preedit text before inserting text in _edje_entry_text_markup_set

[Tom H. <tom...@pa...>]

Dear Jihoon,

I don't know this code very good, but calling 'ecore_main_loop_iterate'
looks bad to me. Isn't there an ecore_imf_context_abort/clear that can
be called before reset so there'll be nothing to commit? If not, we
should probably add something, I think that's the way to go...

--
Tom.

On Thu, 2011-05-19 at 11:47 +0900, Jihoon Kim wrote:
> Hello, EFL developers.
> 
>  
> 
> When elm_entry_entry_set() is called, the preedit text in the entry should
> be cleared. ATM, it doesn’t works so.
> 
> This patch will resolve this problem.
> 
>  
> 
> When ecore_imf_context_reset() is called, the preedit text in the immodule
> will be committed by calling ‘ecore_imf_context_commit_event_add()’.
> 
> ecore_imf_context_commit_event_add puts the event in ecore event queue, so
> it will be processed in the idle state of ecore loop.
> 
> According to this mechanism, commit text is inserted later, so I use
> ‘ecore_main_loop_iterate();’ for inserting the commit string instantly.
> 
>  
> 
> Would you please review this patch and apply in svn?
> 
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its 
> next-generation tools to help Windows* and Linux* C/C++ and Fortran 
> developers boost performance applications - including clusters. 
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> enlightenment-devel mailing list
> enl...@li...
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel