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? I also discovered my custom quit function needed to return True if I wanted to abort the window being destroyed and it's making me realize I need to gain a deeper understanding of the GObject system. Thanks again! On Tue, Aug 30, 2016 at 5:05 PM, Paul Davis <p...@linuxaudiosystems.com> wrote: > the child should have its own handler, and that handler should return > TRUE. this wil stop propagation up the widget tree. > > On Tue, Aug 30, 2016 at 8:02 PM, Jim Heald <jhdoubleose...@gmail.com> > wrote: > >> Hello, >> >> I have a grid set up where some event boxes are attached. Each eventbox >> (which we'll call a column) contains a box with children (which we'll call >> tiles) that are also eventboxes. >> >> What I want is for right clicking a tile to produce one menu >> (Edit/Delete) whereas right clicking an empty space produces another (which >> would be Add). I set this up and connected the signals, but when I right >> click a tile it produces both the Add menu *and* the Edit/Delete menu. >> >> Therefore, my problem is that right clicking a tile *also* sends the >> button-press signal to the column. >> >> My question is what would be the best way to filter these events to >> ensure the parent isn't receiving its childrens' events? I.e. how can I >> either prevent the parent from receiving a signal from the child or >> possibly in the handler for a column make sure there's no tile at the >> coordinates of the click event? >> >> Thanks! >> >> Jim >> >> _______________________________________________ >> gtk-list mailing list >> gtk-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/gtk-list >> >> >
_______________________________________________ gtk-list mailing list gtk-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-list
