Another issue for the documentation

Hi, The documentation states: [quote] gtk_button_set_alignment has been deprecated since version 3.14 and should not be used in newly-written code. Access the child widget directly if you need to control its alignment. [/quote] Now, while the image can be retrieved with the gtk_button_get_imag

Re: Outdated win32 bundle

2015-07-16 11:17 GMT+02:00 Bálint Réczey : > Hi, > > Is there any chance of getting feedback on the part already > implemented or getting in contact with someone who can install the VM > in GNOME's infrastructure? Ping? > > Cheers, > Balint > > 2015-07-02 17:25 GMT+02:00 Bálint Réczey : >> Hi Emma

Re: What should be used?

Hi; On 29 July 2015 at 18:31, Igor Korot 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 available in GTK+ 3,

Re: What should be used?

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 wrote: > Hi;

Re: GTK3, assign custom keyboard shortcuts for menu items?

Hi; On 29 July 2015 at 17:44, Stefan Salewski wrote: > Is that feature deprecated now? Can not find much useful with Google for > this topic. Yes, the ability to change accelerators directly from the menu has been removed in GTK+ 3.x; it was a "break my application, my documentation, and the Gt

GTK3, assign custom keyboard shortcuts for menu items?

Some years ago I managed to get it working for my Ruby App -- I am not sure if only for GTK2, think it worked for GTK3 also. Not that I need or want it myself, but maybe some users of my application do? As I remember, it was hovering the mouse over a menu item and then pressing the desired keys?

Re: What should be used?

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 acciden

Re: What should be used?

Hi; On 29 July 2015 at 14:55, Stefan Salewski 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 drawing mod

Re: What should be used?

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

Re: What should be used?

Hi; On 29 July 2015 at 12:51, Igor Korot wrote: > Hi, ALL, > The documentation says: > > [quote] > gtk_widget_set_double_buffered has been deprecated since version 3.14 > and should not be used in newly-written code. > This function does not work under non-X11 backends or with non-native > window

What should be used?

Hi, ALL, The documentation says: [quote] gtk_widget_set_double_buffered has been deprecated since version 3.14 and should not be used in newly-written code. This function does not work under non-X11 backends or with non-native windows. It should not be used in newly written code. [/quote] However