Just to let folks know that the pointers here have given me the lead
in that I needed and I've got a working code. (A bit more elegant in
the Gtk3 case than Gtk2 but both work).
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.
Il giorno Fri, 17 Jun 2011 13:09:07 -0500
Michael Cronenworth ha scritto:
> Nicola Fontana on 06/17/2011 12:29 PM wrote:
> > AFAICT there is no such difference between platforms: the documentation
> > explicitely requires a gboolean [1]. I think your program was working on
> > Linux only because
Nicola Fontana on 06/17/2011 12:29 PM wrote:
AFAICT there is no such difference between platforms: the documentation
explicitely requires a gboolean [1]. I think your program was working on
Linux only because of a coincidence or something else outside of the
GTK+ scope.
This could be attributed
Il giorno Fri, 17 Jun 2011 11:56:12 -0500
Michael Cronenworth ha scritto:
> Michael Cronenworth on 06/17/2011 11:46 AM wrote:
> My callbacks were of return type void. Changing them to gboolean and
> returning TRUE makes the window appear upon the second call. It seems in
> Win32 the default is
Hello,
I have a window that I create in a hidden state. When it is accessed in
a menu I call gtk_window_present( window ); and the window is visible. I
have a callback attached to the "destroy" and "delete-event" signals and
I call gtk_widget_hide( window ) in them.
When a user attempts to a
Michael Cronenworth on 06/17/2011 11:46 AM wrote:
Is this a possible bug? or I'm doing something wrong?
And just as I hit send I catch it.
My callbacks were of return type void. Changing them to gboolean and
returning TRUE makes the window appear upon the second call. It seems in
Win32 the d
