callisto-debian/evolution
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

(composer_key_pressed): Don't chain the event

Browse Source 
handler here -- that's just wrong!  Also stop emission of the
signal when we catch Escape.

svn path=/trunk/; revision=17987
This commit is contained in:
Ettore Perazzoli
2002-09-05 17:29:14 +00:00
parent 15af11c988
commit 1fa08a33f8
2 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
composer/ChangeLog
View File

@ -1,3 +1,9 @@
2002-09-05 Ettore Perazzoli <ettore@ximian.com>
* e-msg-composer.c (composer_key_pressed): Don't chain the event
handler here -- that's just wrong! Also stop emission of the
signal when we catch Escape.
2002-09-04 Jeffrey Stedfast <fejj@ximian.com>
* e-msg-composer.c (create_composer): Make it so that the composer

13
composer/e-msg-composer.c
View File

@ -2736,16 +2736,11 @@ composer_key_pressed (GtkWidget *widget, GdkEventKey *event, gpointer user_data)
{
if (event->keyval == GDK_Escape) {
do_exit (E_MSG_COMPOSER (widget));
return TRUE; /* Stop the event? is this TRUE or FALSE? */
gtk_signal_emit_stop_by_name (GTK_OBJECT (widget), "key-press-event");
return TRUE; /* Handled. */
}
/* Have to call parent's handler, or the widget wouldn't get any
key press events. Note that this is NOT done if the dialog
may have been destroyed. */
if (GTK_WIDGET_CLASS (parent_class)->key_press_event)
return (* (GTK_WIDGET_CLASS (parent_class)->key_press_event)) (widget, event);
return FALSE; /* Not handled. */
}