Hi, On Thu, Feb 28, 2008 at 1:31 PM, Matthew Allum <[EMAIL PROTECTED]> wrote: > Check out current trunk, we've been experimenting with the easier but > maybe not so nice route of taking an external display, shutting down > 'automatic' event collection. Im not sure if its enough however. >
Right, this solves one problem but not all problems - the unsolved problem here is allowing GTK to do event dispatch among widgets in a toplevel window. That is, of the widgets in a window, it decides which one should get a key event if any. It also does "bubbling" of events through the hierarchy, and implements the GTK grab mechanism (gtk_grab_add()). The full solution I think is straightforward; have a way to put a ClutterEvent on the event queue, and have the GTK widget implement a GdkEvent-to-ClutterEvent translation which would be inside a GtkWidget::event implementation, or perhaps it should be in individual event handlers (key_press_event, etc.) Then a Clutter widget would behave like a normal GTK widget, event-wise. Havoc -- To unsubscribe send a mail to [EMAIL PROTECTED]
