Re: GTK 3 support status

2012-01-02 Thread tristan . van . berkom
On 2011-12-06, at 8:12 PM, Andrew Cowie and...@operationaldynamics.com wrote: On Tue, 2011-12-06 at 17:47 +0900, Tristan Van Berkom wrote: gtk_widget_set_size_request() should still succeed with the expected behaviour of setting the minimum size of a widget, So, does it do so for

GTK 3 support status

2012-01-02 Thread John Lindgren
Hi, I am wondering what the status of GTK 3 is at this time with regard to bugs reported by application developers. I reported a rather serious bug (https://bugzilla.gnome.org/show_bug.cgi?id=662043) a month and a half ago, and there is still no comment from any GTK developer. The bug

Re: GTK 3 support status

2011-12-06 Thread Tristan Van Berkom
On Tue, Dec 6, 2011 at 1:15 AM, John Lindgren john.lindg...@aol.com wrote: Hi Tristan, This makes a bit more sense now. On 12/05/2011 09:27 AM, Tristan Van Berkom wrote: On Mon, Dec 5, 2011 at 11:18 PM, John Lindgrenjohn.lindg...@aol.com  wrote: It looks to me as though there are 3

Re: GTK 3 support status

2011-12-06 Thread Andrew Cowie
On Tue, 2011-12-06 at 17:47 +0900, Tristan Van Berkom wrote: gtk_widget_set_size_request() should still succeed with the expected behaviour of setting the minimum size of a widget, So, does it do so for GtkLabel? ie, is it acceptable to call it? [this thread has become a bit confusing] AfC

Re: GTK 3 support status

2011-12-05 Thread John Lindgren
On 12/05/2011 02:22 AM, Tristan Van Berkom wrote: On Mon, Dec 5, 2011 at 4:18 PM, Tristan Van Berkomt...@gnome.org wrote: Hi John, I am responsible for a large part of your pain. And I'm also surprised that this code is not working for you. The last time I looked at size negotiation, the

Re: GTK 3 support status

2011-12-05 Thread John Lindgren
It looks to me as though there are 3 separate problems contributing here: 1. GtkLabel does not take into account gtk_widget_set_size_request() when reporting its natural size: https://bugzilla.gnome.org/show_bug.cgi?id=662043 2. Nor does it take into account gtk_label_set_width_chars():

Re: GTK 3 support status

2011-12-05 Thread Tristan Van Berkom
On Mon, Dec 5, 2011 at 10:56 PM, John Lindgren john.lindg...@aol.com wrote: On 12/05/2011 02:22 AM, Tristan Van Berkom wrote: On Mon, Dec 5, 2011 at 4:18 PM, Tristan Van Berkomt...@gnome.org  wrote: Hi John,   I am responsible for a large part of your pain. And I'm also surprised that

Re: GTK 3 support status

2011-12-05 Thread Tristan Van Berkom
On Mon, Dec 5, 2011 at 11:18 PM, John Lindgren john.lindg...@aol.com wrote: It looks to me as though there are 3 separate problems contributing here: 1. GtkLabel does not take into account gtk_widget_set_size_request() when reporting its natural size:

Re: GTK 3 support status

2011-12-05 Thread John Lindgren
Hi Tristan, This makes a bit more sense now. On 12/05/2011 09:27 AM, Tristan Van Berkom wrote: On Mon, Dec 5, 2011 at 11:18 PM, John Lindgrenjohn.lindg...@aol.com wrote: It looks to me as though there are 3 separate problems contributing here: 1. GtkLabel does not take into account

Re: GTK 3 support status

2011-12-05 Thread Costin Chirvasuta
I don't really understand what max-width-chars would be useful for. Can't you set a natural size for a widget instead of a natural max char width? If I want to ellipsize it won't do me any good if ... is the same as I can see there is gtk_set_size_request for setting minimum width,

Re: GTK 3 support status

2011-12-04 Thread Emmanuele Bassi
hi; On 4 December 2011 02:41, John Lindgren john.lindg...@aol.com wrote: I am wondering what the status of GTK 3 is at this time with regard to bugs reported by application developers. the status is always the same: bugs reported will be looked at by the gtk maintainers depending on time.

Re: GTK 3 support status

2011-12-04 Thread Emmanuele Bassi
hi; On 4 December 2011 02:56, Michael Cronenworth m...@cchtml.com wrote: I agree that yours, and a few other GTK3 bugs[1][2], have kept me from porting my apps from GTK2. My suggestion would be to post your e-mail to the gtk-devel list[3], and as a last resort open a bug on the Red Hat

Re: GTK 3 support status

2011-12-04 Thread John Lindgren
On 12/04/2011 04:02 AM, Emmanuele Bassi wrote: the status is always the same: bugs reported will be looked at by the gtk maintainers depending on time. So the status at this moment is that no developers have time to look at bugs reported by application developers. Or is there something wrong

Re: GTK 3 support status

2011-12-04 Thread Tristan Van Berkom
On Mon, Dec 5, 2011 at 9:21 AM, John Lindgren john.lindg...@aol.com wrote: On 12/04/2011 04:02 AM, Emmanuele Bassi wrote: the status is always the same: bugs reported will be looked at by the gtk maintainers depending on time. So the status at this moment is that no developers have time to

Re: GTK 3 support status

2011-12-04 Thread Tristan Van Berkom
On Mon, Dec 5, 2011 at 4:18 PM, Tristan Van Berkom t...@gnome.org wrote: On Mon, Dec 5, 2011 at 9:21 AM, John Lindgren john.lindg...@aol.com wrote: On 12/04/2011 04:02 AM, Emmanuele Bassi wrote: the status is always the same: bugs reported will be looked at by the gtk maintainers depending on

GTK 3 support status

2011-12-03 Thread John Lindgren
Hi, I am wondering what the status of GTK 3 is at this time with regard to bugs reported by application developers. I reported a rather serious bug (https://bugzilla.gnome.org/show_bug.cgi?id=662043) a month and a half ago, and there is still no comment from any GTK developer. The bug

Re: GTK 3 support status

2011-12-03 Thread Michael Cronenworth
On 12/03/2011 08:41 PM, John Lindgren wrote: I am wondering what the status of GTK 3 is at this time with regard to bugs reported by application developers. I reported a rather serious bug (https://bugzilla.gnome.org/show_bug.cgi?id=662043) a month and a half ago, and there is still no

Re: GTK 3 support status

2011-12-03 Thread Kevin DeKorte
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/03/2011 07:41 PM, John Lindgren wrote: Hi, I am wondering what the status of GTK 3 is at this time with regard to bugs reported by application developers. I reported a rather serious bug (https://bugzilla.gnome.org/show_bug.cgi?id=662043)