Re: Re: Re: Re: Button can't be clicked.

2005-12-22 Thread zun03127
Billy, Yes, It's fine to me. This can be one of my candidates of this solution. By the way, do you have any idea of the situation your mention Might work depending on the situation. If you have, please please give me what you have. Your answer would be greatly appreciated. And... Do you know

missing GMainContext methods ... (fwd)

2005-12-22 Thread Tim Janik
hey michael, you really need to check your subscription information, this one didn't get through either, so i'm forwarding. --- ciaoTJ -- Forwarded message -- Date: Tue, 20 Dec 2005 17:21:07 + From: michael meeks [EMAIL PROTECTED] To: Federico Mena Quintero [EMAIL

Re: Context in translations, Q_() and gettext

2005-12-22 Thread Matthias Clasen
On 12/21/05, James Henstridge [EMAIL PROTECTED] wrote: . One issue with this change is that current xgettext releases probably won't extract strings for the Q2_() form. Ah, you are right. We would have to do some extrs step, like extractig the Q2 calls and convert them to Q in an auxiliary

Re: Context in translations, Q_() and gettext

2005-12-22 Thread Mart Raudsepp
Matthias Clasen wrote: On 12/21/05, James Henstridge [EMAIL PROTECTED] wrote: . One issue with this change is that current xgettext releases probably won't extract strings for the Q2_() form. Ah, you are right. We would have to do some extrs step, like extractig the Q2 calls and convert them

Re: Context in translations, Q_() and gettext

2005-12-22 Thread James Henstridge
Mart Raudsepp wrote: Matthias Clasen wrote: On 12/21/05, James Henstridge [EMAIL PROTECTED] wrote: . One issue with this change is that current xgettext releases probably won't extract strings for the Q2_() form. Ah, you are right. We would have to do some extrs step, like extractig the

Re: Context in translations, Q_() and gettext

2005-12-22 Thread Federico Mena Quintero
On Thu, 2005-12-22 at 11:02 +0800, James Henstridge wrote: One issue with this change is that current xgettext releases probably won't extract strings for the Q2_() form. How does that work? Does it grep for start of symbol optional single letter underscore

g_object_ref_sink and GUnowned

2005-12-22 Thread Tim Janik
as a result of the recent GTK_FLOATING broken in 2.9? discussion: http://mail.gnome.org/archives/gtk-devel-list/2005-December/msg00107.html as well as the ABI and API for g_object_ref_sink() discussion: http://mail.gnome.org/archives/gtk-devel-list/2005-December/msg00174.html i've now

Re: missing GMainContext methods ... (fwd)

2005-12-22 Thread Tim Janik
On Thu, 22 Dec 2005, michael meeks wrote: -- Forwarded message -- Date: Tue, 20 Dec 2005 17:21:07 + From: michael meeks [EMAIL PROTECTED] To: Federico Mena Quintero [EMAIL PROTECTED], Tim Janik [EMAIL PROTECTED] Cc: Gtk Hackers gtk-devel-list@gnome.org Subject: missing

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Owen Taylor
On Thu, 2005-12-22 at 17:49 +0100, Tim Janik wrote: GUnowned derives from GObject, has intiially a floating ref_count. I hate to quibble names, but it seems really strange to have a class GUnowned where instances are normally owned. (In fact, the goal of anybody using a GUnowned has to be to

Re: missing GMainContext methods ... (fwd)

2005-12-22 Thread Owen Taylor
On Thu, 2005-12-22 at 18:20 +0100, Tim Janik wrote: On Thu, 2005-11-17 at 16:57 +, michael meeks wrote: So - I've been trying to use the GMainContext to fix a rather tricky issue in using unsafe single-threaded code accessed via ORBit2 from multiple OO.o threads in a safe

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Yevgen Muntyan
Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually neccessary), that i decided to simply sponsor an object type if that helps the majority to understand which

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Tim Janik
On Thu, 22 Dec 2005, Yevgen Muntyan wrote: Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually neccessary), that i decided to simply sponsor an object type if