Re: Documentation inconsistency

2015-08-19 Thread Rafał Lużyński
Hi, On 5 Aug 2015, 06:59 Igor Korot ikoro...@gmail.com wrote: [...] I can turn it off for GTK+-2.32+ (no replacement, right?), but I want to make sure it's a right thing to do. In case you have missed this: g_thread_init() belongs to GLib, not GTK+, so all comments about the versions apply

Re: Another documentation inconsistency

2015-08-10 Thread Emmanuele Bassi
Hi; On 8 August 2015 at 05:29, Igor Korot ikoro...@gmail.com wrote: Hi, ALL, The documentation states: [quote] Adds an activatable widget to the action area of a GtkDialog, connecting a signal handler that will emit the “response” signal on the dialog when the widget is activated. The

Re: Another documentation inconsistency

2015-08-10 Thread Igor Korot
Emmanuele, On Mon, Aug 10, 2015 at 4:11 AM, Emmanuele Bassi eba...@gmail.com wrote: Hi; On 8 August 2015 at 05:29, Igor Korot ikoro...@gmail.com wrote: Hi, ALL, The documentation states: [quote] Adds an activatable widget to the action area of a GtkDialog, connecting a signal handler

Re: Another documentation inconsistency

2015-08-09 Thread Daniel Espinosa
May is better if you file a bug about your issue. Then developers could know. track and fix your issues. El ago. 7, 2015 11:29 PM, Igor Korot ikoro...@gmail.com escribió: Hi, ALL, The documentation states: [quote] Adds an activatable widget to the action area of a GtkDialog, connecting a

Re: Documentation inconsistency

2015-08-05 Thread Igor Korot
Hi, On Wed, Aug 5, 2015 at 1:50 AM, Gergely Polonkai gerg...@polonkai.eu wrote: Hello, if you are sure your software will never be compiled against older versions of GLib, then you can take it off. It's really not needed. The fact vtable is mentioned for versions 2.32+ is because you can

Re: Documentation inconsistency

2015-08-05 Thread Paul Davis
On Wed, Aug 5, 2015 at 7:04 AM, Igor Korot ikoro...@gmail.com wrote: Well the trouble is that documentation gives incorrect information: First it says function is deprecated and then gives an impression it's OK to use it. That's the impression you got. It isn't the impression I got. The

Re: Documentation inconsistency

2015-08-05 Thread Gergely Polonkai
I must agree with Paul here. Try to look at the documentation like this: {The warning. Ignore it for now, but we will come back here soon} The usage. This is how you can and should use the function. It states the behaviour of the function for pre-2.24 and post-2.32 versions. You must consider

Re: Documentation inconsistency

2015-08-05 Thread Igor Korot
OK, thx for explanation. On Wed, Aug 5, 2015 at 9:59 AM, Gergely Polonkai gerg...@polonkai.eu wrote: I must agree with Paul here. Try to look at the documentation like this: {The warning. Ignore it for now, but we will come back here soon} The usage. This is how you can and should use the

Re: Documentation inconsistency

2015-08-05 Thread Jasper St. Pierre
I definitely think the wording can be improved. I'll take a shot at it later today -- thanks for the report. On Wed, Aug 5, 2015 at 7:38 AM, Igor Korot ikoro...@gmail.com wrote: OK, thx for explanation. On Wed, Aug 5, 2015 at 9:59 AM, Gergely Polonkai gerg...@polonkai.eu wrote: I must agree

Documentation inconsistency

2015-08-04 Thread Igor Korot
Hi, ALL, The documentation here: states [quote] g_thread_init () void g_thread_init (gpointer vtable); g_thread_init has been deprecated since version 2.32 and should not be used in newly-written code. This function is no longer necessary. The GLib threading system is automatically initialized

Re: Documentation inconsistency

2015-08-04 Thread Gergely Polonkai
Hello, if you are sure your software will never be compiled against older versions of GLib, then you can take it off. It's really not needed. The fact vtable is mentioned for versions 2.32+ is because you can still use it; it didn't disappear (yet), it's just deprecated. Best, Gergely On 5 Aug