StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8100787
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-11-11T22:32:50.860
FavoriteCount
0
LastActivityDate
2011-11-11T22:32:50.860
LastEditDate
LastEditorUserId
0
OwnerUserId
70584
ParentId
8065217
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I'll paste a summary of how gtk_window_key_press_event() works: <pre><code>gboolean gtk_window_propagate_key_event (GtkWindow *window, GdkEventKey *event) { gboolean handled = FALSE; focus = window->focus_widget; while (!handled) { GtkWidget *parent; handled = gtk_widget_event (focus, event); focus = gtk_widget_get_parent (focus); } return handled; } static gint gtk_window_key_press_event (GtkWidget *widget, GdkEventKey *event) { GtkWindow *window = GTK_WINDOW (widget); gboolean handled = FALSE; /* handle mnemonics and accelerators */ if (!handled) handled = gtk_window_activate_key (window, event); /* handle focus widget key events */ if (!handled) handled = gtk_window_propagate_key_event (window, event); /* Chain up, invokes binding set */ if (!handled) handled = GTK_WIDGET_CLASS (gtk_window_parent_class)->key_press_event (widget, event); return handled; } </code></pre> This basically means: <ol> <li>See if the key is appropriate for a mnemonic (i.e. labels that have underlines) or an accelerator (from GtkAccelGroup).</li> <li>Starting from the focused widget and going up the container hierarchy, see if some widget handles the keypress.</li> <li>Pass on the keypress to the parent class of GtkWindow. The closest parent that handles that is GtkWidget, and it does so by dealing with bindings (from gtk_binding_entry_add()).</li> </ol> As you said, simply doing g_signal_connect() to the key-press-event signal of GtkWindow will give you all keypresses that happen when that window is focused. Try doing g_signal_connect_after() instead. This will effectively add another fallback to the sequence above - it means, "run my signal handler after the default one". Note that you'll be catching all unhandled keypresses (e.g. if someone presses a function key that your app doesn't handle), so don't assume that the only thing that gets through to your handler is coming from your barcode scanner.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I only act on keyboard events no other widget wants?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFederico Mena-Quintero
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I only act on keyboard events no other widget wants?
 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
 VTAcceptedByOriginator
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.