GNOME.org
 

Gtkmm-forge Digest, Vol 13, Issue 5

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 443586] Introduction to TreeView is misleading
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   3. [Bug 396157] GInitiallyUnowned-support in glibmm
      (glibmm (bugzilla.gnome.org))
   4. [Bug 396963] Add Glib::signal_idle().connect_once()
      (glibmm (bugzilla.gnome.org))
   5. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   6. [Bug 396157] GInitiallyUnowned-support in glibmm
      (glibmm (bugzilla.gnome.org))
   7. [Bug 441822] X Memory leaks when using GTK+.
      (gtk+ (bugzilla.gnome.org))
   8. [Bug 386180] Reference counting errors with shared
      ActionGroups among Windows (gtkmm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Sun, 10 Jun 2007 11:40:35 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 443586] Introduction to TreeView is
	misleading
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610114035 073C26C41FE box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=443586

  gtkmm | documentation | Ver: unspecified




------- Comment #2 from Robert Pearce  2007-06-10 11:40 UTC -------
> Exactly what part of the text do you mean? I can't see anything that explicitly
> suggests that it should be static.

Did I say explicitly?

The example code extract shows a class declaration. In the absence of any
indication to the contrary, this would normally be expected to live at the top
level. Thus the instantiation that follows would be a static one. That's
certainly how I read it. If there is a good reason why a class should be
declared only within a restricted scope (particularly within the scope of
another class declaration), I would think it worth mentioning that. Especially
if the consequences of doing it wrong can be obscure or not show up until
months later.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=443586.



------------------------------

Message: 2
Date: Sun, 10 Jun 2007 15:24:42 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610152442 7CE146C4205 box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com




------- Comment #2 from Murray Cumming  2007-06-10 15:24 UTC -------
Patches are welcome. Is this only a problem when using the returned connection
object?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

Message: 3
Date: Sun, 10 Jun 2007 15:25:29 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396157] GInitiallyUnowned-support in
	glibmm
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610152529 C9D506C4205 box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396157

  glibmm | object | Ver: unspecified




------- Comment #4 from Murray Cumming  2007-06-10 15:25 UTC -------
An update would be nice.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396157.



------------------------------

Message: 4
Date: Sun, 10 Jun 2007 15:27:17 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396963] Add
	Glib::signal_idle().connect_once()
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610152717 265A36C41FE box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396963

  glibmm | main loop | Ver: 2.13.x




------- Comment #2 from Murray Cumming  2007-06-10 15:27 UTC -------
A patch would be welcome.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396963.



------------------------------

Message: 5
Date: Sun, 10 Jun 2007 15:34:19 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610153419 9F7D76C41EA box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x




------- Comment #3 from Daniel Elstner  2007-06-10 15:34 UTC -------
(In reply to comment #2)
> Is this only a problem when using the returned connection object?

Unfortunately, no, since at least the destructor is always invoked.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

Message: 6
Date: Sun, 10 Jun 2007 17:28:12 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396157] GInitiallyUnowned-support in
	glibmm
To: gtkmm-forge lists sourceforge net
Message-ID: <20070610172812 C99E26C4213 box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396157

  glibmm | object | Ver: unspecified




------- Comment #5 from Philipp Kerling  2007-06-10 17:28 UTC -------
Well, I don't really know if this is completely right or not, and it has been
some time since I wrote this, so I should take another look at this. Basically
it's just about moving some stuff of Gtk::Object to where it belongs:
Glib::InitiallyUnowned. Then Gtk::Object should no longer derive from
Glib::Object but Glib::InitiallyUnowned, as it does in the original libraries 
anyway.
I think some serious testing is required to make sure this thing works well.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396157.



------------------------------

Message: 7
Date: Mon, 11 Jun 2007 01:19:41 +0000 (UTC)
From: "gtk+ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 441822] X Memory leaks when using GTK+.
To: gtkmm-forge lists sourceforge net
Message-ID: <20070611011941 AF2196C4186 box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=441822

  gtk+ | general | Ver: 2.8.x

Matthias Clasen changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mclasen redhat com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |NOTGNOME




------- Comment #2 from Matthias Clasen  2007-06-11 01:19 UTC -------
Nothing concrete here to go on.  The one actual memory leak that can be spotted
among the pages of "still reachable" memory is acutally in libc 


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=441822.



------------------------------

Message: 8
Date: Tue, 12 Jun 2007 16:19:53 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 386180] Reference counting errors with
	shared	ActionGroups among Windows
To: gtkmm-forge lists sourceforge net
Message-ID: <20070612161953 7CF216C4358 box gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=386180

  gtkmm | general | Ver: 2.4

Martin Nordholts changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |NOTABUG




------- Comment #12 from Martin Nordholts  2007-06-12 16:19 UTC -------
Yes that would probably work, and if not some other way will. (I currently
don't have the time to dig into this problem)

I think the main point is that there should be a warning (as you've already
pointed out in bug #429970) when one tries to do what I tried to do.

I will close this as NOTABUG and pass on the problem to bug #429970.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=386180.



------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 13, Issue 5
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]