Michael Cronenworth wrote:
> $ rpm -q gtk2
> gtk2-2.16.5-1.fc11.x86_64
Yup, that's it. 2.16 is the latest stable GTK+ available (2.18 isn't
quite released yet)
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailm
Boggess Rod on 08/13/2009 10:39 AM wrote:
> It's either already be resolved in a newer release, or it
> exists only as an HPUX implementation issue. I may contact HP, but it
> doesn't belong on the Gtk bug list.
>
HP provides an update. I'd get off version 2.6 and onto 2.16 ASAP. Tell
your supe
c: Gtk app list
> Subject: Re: Regarding example code (was Why is ChangeValue reentrant)
>
> Boggess Rod wrote:
> >> In cases like this, you probably have to hack around the
> problem/bug.
> >> IE solve your use case in a different way.
> >
> > Already have.
Michael Torrie on 08/13/2009 10:31 AM wrote:
> I'm on Fedora 11 with GTK 2.18 I think.
$ rpm -q gtk2
gtk2-2.16.5-1.fc11.x86_64
;)
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Boggess Rod wrote:
>> In cases like this, you probably have to hack around the problem/bug.
>> IE solve your use case in a different way.
>
> Already have. Instead of using the response from gtk_dialog_run, I
> gtk_widget_show_all the dialog window and return TRUE from the
> change-value callback
Boggess Rod wrote:
> It should be attached to one of the messages I posted on this thread.
> If you're interested, here's another copy of it.
Will take a brief look at it.
> I have NOT tested this on a newer version of Gtk (can't). I'm hoping
> someone else out there will be kind enough to test
Boggess Rod wrote:
> Sorry, I did post a small example that demonstrates the unusual (buggy?)
> behavior in a follow-up post. The more I dug into it, the weirder it
> became, and the more convinced I am that it's a bug in Gtk. Or at
> least, a bug in the HPUX implementation of it. I'm waiting ab
Sorry, I did post a small example that demonstrates the unusual (buggy?)
behavior in a follow-up post. The more I dug into it, the weirder it
became, and the more convinced I am that it's a bug in Gtk. Or at
least, a bug in the HPUX implementation of it. I'm waiting about a week
to see if I hear
Well, I was going to post a simple case showing the problem. Only, it
works in the simple case. This just keeps getting more and more
bizarre. I created a top level window, added an hscale, and the
change-value signal hander. Inside the signal handler, I create a
message dialog, do a dialog_run
