Hi Stefan,
I am also in the process of converting my app from v2 to v3, where I do
*lots* of drawing. So before jumping in, I decided to revisit a drawing
example I posted some years ago to first convert it to v3 and its drawing
to Cairo.
In the hope of being useful for others, I have posted
Emmanuel,
I asked on the other thread but nobody replied :(
What is the minimum GTK+ version for GtkLinkButton signnal activate-link.
And how to stop propagating the click on it with GTK+2 where this is
not available?
Thank you.
On Wed, Jul 29, 2015 at 10:12 AM, Emmanuele Bassi
On Wed, 2015-07-29 at 15:12 +0100, Emmanuele Bassi wrote:
Those examples, especially the one that uses Unix signals to interrupt
the program flow, ought to be burned with fire. Not only they are
questionable in GTK 2.x, but they are also unportable jumbles of code
that work by sheer accident.
Hi;
On 29 July 2015 at 18:31, Igor Korot ikoro...@gmail.com wrote:
Emmanuel,
I asked on the other thread but nobody replied :(
Don't hijack threads; it makes searching the archives impossible.
What is the minimum GTK+ version for GtkLinkButton signnal activate-link.
Since it's only
]
However it does not say what should be used instead.
Could somepone please clarify?
Thank you.
___
gtk-list mailing list
gtk-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-list
-native
windows. It should not be used in newly written code.
[/quote]
However it does not say what should be used instead.
Nothing should be used instead.
All widgets inside GTK are double-buffered, and all windowing systems
are double buffering the drawing surfaces used to present things
On Wed, 2015-07-29 at 13:05 +0100, Emmanuele Bassi wrote:
If you have legacy code that requires disabling double buffering, you
should probably invest some time into porting it to a proper solution
integrated with the GTK drawing model;
It would be great if someone could port this example to
Hi;
On 29 July 2015 at 14:55, Stefan Salewski m...@ssalewski.de wrote:
On Wed, 2015-07-29 at 13:05 +0100, Emmanuele Bassi wrote:
If you have legacy code that requires disabling double buffering, you
should probably invest some time into porting it to a proper solution
integrated with the GTK
