Fixed the bug to use the wrong g_text_input value.

There is the possibility to use the wrong g_text_input value even if it was deactivated.
When input_method is unbinded or input_method_context is created temporarily to send input_panel_hide event,
the g_text_input value is not initialized as null.
This cause that the wrong g_text_input value is used in the other function.

Change-Id: I088fa219e5632748451c326790d10d3f1c62401a

diff --git a/src/e_mod_main.c b/src/e_mod_main.c
index cc4223491d2c5ddbde0dbd5e7dc4c3a0917fe2cc..f6d660eb02bc23c47a5d97cd6b564e8d40b708f1 100644 (file)
--- a/src/e_mod_main.c
+++ b/src/e_mod_main.c
@@ -1011,6 +1011,12 @@ _e_mod_ecore_key_down_cb(void *data, int type, void *event)
 static void
 _e_text_input_deactivate(E_Text_Input *text_input, E_Input_Method *input_method, Eina_Bool need_focus_in)
 {
+   if (text_input == g_text_input)
+     {
+        g_text_input = NULL;
+        g_client = NULL;
+     }
+
    if (input_method->input == text_input)
      {
         if ((input_method->context) && (input_method->resource))