Re: Parent receiving child's button press event
- From: Timm Bäder <mail baedert org>
- To: Nicola Fontana <ntd entidi it>
- Cc: Paul Davis <paul linuxaudiosystems com>, ML-gtk <gtk-list gnome org>
- Subject: Re: Parent receiving child's button press event
- Date: Wed, 31 Aug 2016 09:40:35 +0200
On 31.08, Nicola Fontana wrote:
Il Tue, 30 Aug 2016 17:48:34 -0700 Jim Heald <jhdoubleoseven gmail com> scrisse:
Thank you so much! It's literally these return True things that keep
throwing me off.
Do you have a suggestion of somewhere I can read about all of these
conventions?
...
They are not conventions, they are documented behavior: just pay
attention to the signal documentation. In your specific case you
probably connected a callback to the "button-press-event" signal.
Citing the relevant documentation [1]:
Returns: TRUE to stop other handlers from being invoked for
the event. FALSE to propagate the event further.
I think this is respected for all "*-event" signals.
[1] https://developer.gnome.org/gtk3/stable/GtkWidget.html#GtkWidget-button-press-event
Ciao.
--
Nicola
Only some of the docs for these signals have been updated, but please use
GDK_EVENT_PROPAGATE or GDK_EVENT_STOP instead. Same for mainloop
sources, where you should use G_SOURCE_CONTINUE and G_SOURCE_REMOVE.
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]