StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16263184
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-28T13:06:40.833
FavoriteCount
0
LastActivityDate
2013-04-28T13:06:40.833
LastEditDate
LastEditorUserId
0
OwnerUserId
2298336
ParentId
16119911
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The example code you show has two problems. <ul> <li>First, you say "I have an Gtk::EventBox with two events connected." But in your example you connect to MyWindow's events, and leave the EventBox's events unconnected.</li> <li>An EventBox allows you to receive events, but you still have to explicitly say which events you want to receive.</li> </ul> This is the corrected code: <pre><code>#include <gtkmm.h> #include <iostream> class MyWindow : public Gtk::Window { Gtk::EventBox event_box; bool event_box_button_press(GdkEventButton *b) { std::cout << "button press" << std::endl; return false; } bool event_box_scroll(GdkEventScroll *e) { std::cout << "scrollEvent" << std::endl; return false; } public: MyWindow () { event_box.add_events(Gdk::BUTTON_MOTION_MASK); event_box.add_events(Gdk::SCROLL_MASK); event_box.signal_button_press_event().connect( sigc::mem_fun(*this, &MyWindow::event_box_button_press)); event_box.signal_scroll_event().connect( sigc::mem_fun(*this, &MyWindow::event_box_scroll)); add(event_box); set_default_size(640, 480); show_all(); } }; int main(int argc, char** argv) { Gtk::Main kit(argc, argv); MyWindow window; kit.run(window); return 0; } </code></pre> Some notes on this code: <ul> <li>I've omitted the ScrolledWindow, as that is irrelevant to the example. You don't need it to catch scroll events. You can add it back if you actually need a scrolled window for your application.</li> <li>The code would probably be neater if you derive a custom EventBox with the behavior you need. I didn't do this to stay closer to your original code.</li> <li>See <a href="https://developer.gnome.org/gtkmm-tutorial/3.2/sec-connecting-signal-handlers.html.en" rel="nofollow">this documentation</a> for information on connecting signals and the <code>sigc::mem_fun</code> stuff.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGtkmm scroll_event do not work when a button is pressed
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USpdw
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGtkmm scroll_event do not work when a button is pressed
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.