On Fri, Dec 06, 2002 at 08:04:33AM +, Diego Zuccato wrote:
> What I still can't understand is HOW IN THE H..L the multithreaded
> version could completly block mouse activity even out of the program
> window when I did a gtk_widget_set sensitive() on a ctree :-( Just it!
> If I removed the set_
Havoc Pennington wrote:
> Yes, it's normal. If you ask to have your callback invoked whenever
> the fd is ready for writing, and it's always ready, then your callback
> will be invoked continuously eating 100% CPU. That doesn't seem so
> surprising - you get what you ask for. ;-)
Yep. Once underst
On Thu, Dec 05, 2002 at 11:13:36PM +, Diego Zuccato wrote:
> int main( int argc,
> char *argv[] )
> {
> GtkWidget *window;
> gtk_init (&argc, &argv);
> window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
> w=gtk_button_new_with_label("Prova!");
> gtk_container_add(GTK
Hello.
I'm using Gtk+-1.2.10.
Developing a db access framework, I discovered (after LONG tracing :-( )
that it seems g_io_add_watch can block (at least partially) widgets
redraw.
This is a quick example (derived from base.c):
#include
gboolean cbk(GIOChannel *ch, GIOCondition cond, gpointer ptr
