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.
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
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
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
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
hi;
On 4 December 2011 13:23, Benjamin Otte o...@gnome.org wrote:
Tristan Van Berkom tvb at gnome.org writes:
Yes, real-world well-written GObjects *must* not crash after being disposed,
code that crashes because apis are called after dispose time are bugs,
and you should fix them as
What we probably also should do is deprecate one of the two
virtual functions, so people use the same one to clean up everywhere.
That would be a _really_ bad idea.
_finalize gets rid of the last fragments of the object. Since random
code could have obtained refs to the object, the object
On Sun, Dec 04, 2011 at 01:40:58PM +, Emmanuele Bassi wrote:
this is, of course, not true: GNOME is full of badly written GObject
code, mostly because it has been written at various stages of the
learning process of various people. plus, the documentation is not
entirely clear in a lot
2011/12/5 David Nečas y...@physics.muni.cz:
On Sun, Dec 04, 2011 at 01:40:58PM +, Emmanuele Bassi wrote:
this is, of course, not true: GNOME is full of badly written GObject
code, mostly because it has been written at various stages of the
learning process of various people. plus, the
I would be somewhat tempted to listen to all the stuff you're saying
below. But then I looked at the code you maintain[1], and I realized
it doesn't do anything of that. So I'm inclined to think that what
you're talking about is more about an ideal world that you wish we all
aspired to, but is not
Benjamin Otte o...@gnome.org wrote:
But then I looked at [gnumeric] and I realized
it doesn't do anything of that. So I'm inclined to think that what
you're talking about is more about an ideal world that you wish we all
aspired to, but is not in any way related to how people write code in
11 matches
Mail list logo
