On Wed, 2008-07-09 at 11:56 +0200, Toralf Lund wrote: > richard boaz wrote: > > not sure what's could be going wrong since you didn't supply any code, > > but... > I thought I would ask some fundamental questions before I presented a > lot of complex code that would more likely than not only confuse > everyone... Or alternatively, I don't want to spend time on writing a > simple example before I know if the functionality is actually expected > to work... > > first, see the accelerator documentation: > > > > http://library.gnome.org/devel/gtk/stable/gtk-Keyboard-Accelerators.html#gtk-accelerator-set-default-mod-mask > > > > and to "see" if the ALT key is pressed, in your mouse callback: > Ah, but it's not the ALT key I don't see, it's the actual button > click/release. That is, the callback simply isn't called, so if I do: > > gboolean mouse(GtkWidget *widget, GdkEventButton *event, gpointer nil) > { > fprintf(stderr, "This is the mouse callback\n"); > > } > > I simply don't see the text on the console when I press the button. Or > that is, I know the events are caught in the sense that I do get the > printout if I press the button alone, or even along with Ctrl or Shift. > But, once Alt is down, I can click away as much as I like, I just don't > see anything no matter what. > > - Toralf > Could it simply be your windowmanager eating the ALT key presses? I know that metacity I believe by default does that on my GNOME desktop. I had to configure it not to, to be able to use any key-shortcuts involving the ALT key in Blender, for example. _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
