GNOME Bugzilla – Bug 303873
unable to commit through 'enter' in calendar
Last modified: 2008-01-14 20:21:36 UTC
Distribution/Version: FC Description of problem: At the moment, it is not possible to commit ja characters with Enter using CannaLE from IIIMF. How reproducible: Always Steps to Reproduce: 1.in g-t, LANG=ja_JP.UTF-8 evolution 2.select Calendar 3.click on any of the time slot 4.press a, backspace 5.ctrl-space 6.sushi 7.enter Actual results: Blank, unable to commit the ja character Expected results: Able to commit the ja char Additional info: Only exist for ja locale. Tried zh_*/ko and other indic locales as well.
Adding keyword
Lawrence: Can you please try with latest version ?
This problem still happens with the latest version. for more info, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154360
there's a patch available at redhat bugzilla for evo-2.2. so is this still valid with evo2.4? please REOPEN then.
Still valid. Pleaese use test im module in bug 321310. If you use this module, you can see the issue. Many Fedora users use SCIM, so they think the issue has gone. But sill here. SCIM use gtk_key_snooper_install to get key event before widget getting key event, so the issue does not happen.
hiroyuki, thanks a lot for testing this. does applying the redhat patch help/fix this?
I'm sorry, I didn't look the patch yet. I'll do it soon.
I looked the patch briefly. Tagoh san, can you use g_signal_connect_after? If you use it, "Return" key press event is not robbed by EDayView. Isn't it?
I confirmed that this bug has fixed only the following change. But another bug happens. The bug is that focus entry does not move to next entry when "Return" key is pressed. Just LF is fed in editing entry. Neverthless, I think this approach is right. EText widget should have property such as "Multi-Line", and if the value is FALSE, "activate" signal is emitted when "Return" key is pressed like GtkEntry does. EDayView gets the "activate" signal, then move its focus to next entry. diff -u -p -r1.298 e-day-view.c --- e-day-view.c 4 May 2006 15:14:24 -0000 1.298 +++ e-day-view.c 13 Jun 2006 02:38:51 -0000 @@ -4469,7 +4473,8 @@ e_day_view_reshape_long_event (EDayView NULL); g_object_set_data (G_OBJECT (event->canvas_item), "event-num", GINT_TO_POINTER (event_num)); g_object_set_data (G_OBJECT (event->canvas_item), "event-day", GINT_TO_POINTER (E_DAY_VIEW_LONG_EVENT)); - g_signal_connect (event->canvas_item, "event", + + g_signal_connect_after (event->canvas_item, "event", G_CALLBACK (e_day_view_on_text_item_event), day_view); g_signal_emit_by_name (G_OBJECT(day_view), "event_added", event); @@ -4656,7 +4661,8 @@ e_day_view_reshape_day_event (EDayView * NULL); g_object_set_data (G_OBJECT (event->canvas_item), "event-num", GINT_TO_POINTER (event_num)); g_object_set_data (G_OBJECT (event->canvas_item), "event-day", GINT_TO_POINTER (day)); - g_signal_connect (event->canvas_item, "event", + + g_signal_connect_after (event->canvas_item, "event", G_CALLBACK (e_day_view_on_text_item_event), day_view); g_signal_emit_by_name (G_OBJECT(day_view), "event_added", event);
It looks like this was fixed in Evolution 2.21.5 by bug #264404. Closing as a duplicate. *** This bug has been marked as a duplicate of 264404 ***