Re: a bunch of issues

["Michal \"Gleba\" Ziemski" <gtk roo k pl>]

 > > * Is it possible to force the focus to stay on the widget (GtkEntry) =
 > >after the user pressed TAB?
 >
 > handle the key_press and key_release events, return TRUE if the key is
 > one that you don't want handled by the normal mechanism.

 Well, this should work fine. But there may be more than one key combination
 to
 leave the widget (i.e. mnemonics on other widgets or some fancy accel
 table).
 Furthermore the user still can mischievously click in another widget thus
 mocking the programmer. Any ideas how to disallow that?

 > > * Do both signals and events require gdk_threads_enter() in a =
 > >multithreaded app?
 >
 > every single call to any Xlib, glib, gdk or gtk function requires
 > protection by the mutex. thats because although GTK itself won't cause
 > multiple calls to handlers etc. during event handling, other threads
 > may be active and making GTK etc. calls.
 >

 AFAIK gtk_main() calls gdk_threads_enter() itself. What I have been able to
 quess
 from the API documentation is that gdk_threads_leave() is called before
 entering the event handler.
 I just want to know if the same applies to signal handlers.

 I appreciate your help.
 Regards!
 Michal "Gleba" Ziemski