Send Gtkmm-forge mailing list submissions to
        [email protected]

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
        [email protected]

You can reach the person managing the list at
        [email protected]

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 580310] cannot pass NULL env to spawn_async()
      (glibmm (bugzilla.gnome.org))
   2. [Bug 587895] spawn_async cannot inherit parent    working
      directory (glibmm (bugzilla.gnome.org))
   3. [Bug 588024] New: incomplete doxygen documentation        (missing
      links) (gtkmm (bugzilla.gnome.org))
   4. [Bug 588024] incomplete doxygen documentation     (missing links)
      (gtkmm (bugzilla.gnome.org))
   5. [Bug 518002] Custom Container example prints      warnings on
      terminal (gtkmm (bugzilla.gnome.org))
   6. [Bug 518002] Custom Container example prints      warnings on
      terminal (gtkmm (bugzilla.gnome.org))
   7. [Bug 518002] Custom Container example prints      warnings on
      terminal (gtkmm (bugzilla.gnome.org))


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

Message: 1
Date: Mon,  6 Jul 2009 14:14:33 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 580310] cannot pass NULL env to
        spawn_async()
To: [email protected]
Message-ID: <[email protected]>
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=580310

  glibmm | general | Ver: 2.4.x

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |NOTABUG
            Summary|spawn_async                 |cannot pass NULL env to
                   |                            |spawn_async()




------- Comment #1 from Daniel Elstner  2009-07-06 14:14 UTC -------
The documentation is auto-generated from the C API documentation and thus
sometimes confusing in the manner you experienced.

But you can simply use the other spawn_async() overload which doesn't take the
env vector argument:
<http://www.gtkmm.org/docs/glibmm-2.4/docs/reference/html/group__Spawn.html#g0c4e1708989b50fb34266504cc038ee6>


-- 
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=580310.



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

Message: 2
Date: Mon,  6 Jul 2009 15:09:01 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 587895] spawn_async cannot inherit
        parent  working directory
To: [email protected]
Message-ID: <[email protected]>
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=587895

  glibmm | general | Ver: unspecified

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
         AssignedTo|gtkmm-                      |[email protected]
                   |[email protected] |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
         OS/Version|Linux                       |All




------- Comment #1 from Daniel Elstner  2009-07-06 15:08 UTC -------
Just pushed this to master:

2009-07-06  Daniel Elstner  <[email protected]>

        Treat empty Glib::spawn*() working dir as unset

        * glib/src/spawn.ccg (Glib::spawn_async_with_pipes): If the
        working_directory argument is the empty string, pass a 0 pointer
        to the GLib C API to make it inherit the parent's working directory.
        This is fine as the empty string is not a valid directory name, and
        our documentation already says that it will be interpreted that way.
        (Glib::spawn_async): ditto,
        (Glib::spawn_sync): ditto.

I have not merged it into any of the stable branches yet, however.


-- 
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=587895.



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

Message: 3
Date: Tue,  7 Jul 2009 21:22:56 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 588024] New: incomplete doxygen
        documentation   (missing links)
To: [email protected]
Message-ID: <[email protected]/>
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=588024

  gtkmm | documentation | Ver: unspecified
           Summary: incomplete doxygen documentation (missing links)
           Product: gtkmm
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: documentation
        AssignedTo: [email protected]
        ReportedBy: [email protected]
     GNOME version: Unspecified
   GNOME milestone: Unspecified


The Gtkmm API documentation pages are missing some links to doxygen generated
content.

The content is on the server (links can be constructed manually):

http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/annotated.html
http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/functions.html
http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/hierarchy.html
http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/inherits.html

but there aren't any links to it anywhere on the pages accessable from the main
documentation page. These links should probably go into the heading.

Note: I am aware that the Gtkmm documentation does have a widget list. But not
every class is a widget. And since the class list is already there, it wouldn't
hurt to link it IMHO.


-- 
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=588024.



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

Message: 4
Date: Tue,  7 Jul 2009 21:27:29 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 588024] incomplete doxygen
        documentation   (missing links)
To: [email protected]
Message-ID: <[email protected]>
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=588024

  gtkmm | documentation | Ver: unspecified

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]




-- 
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=588024.



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

Message: 5
Date: Wed,  8 Jul 2009 20:43:23 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 518002] Custom Container example prints
        warnings on terminal
To: [email protected]
Message-ID: <[email protected]>
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=518002

  gtkmm | general | Ver: unspecified

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
         OS/Version|Linux                       |All




------- Comment #3 from Daniel Elstner  2009-07-08 20:43 UTC -------
Fixed the fix. :-)

commit 4474ebb25f0309bb88e890b118db78beed5261d5
Author: Daniel Elstner <[email protected]>
Date:   Wed Jul 8 21:43:40 2009 +0200

    Correct base type check in Container_Class::remove_callback()

    * gtk/src/container.ccg (Gtk::Container_Class::remove_callback):
    In order to test for the abstract GtkContainer parent class, actually
    compare against the parent type instead of making invalid assumptions
    about the derived type.  By means of the alternative Glib::ObjectBase
    constructor, it is possible to create a custom GObject type different
    from the standard one.

Pushed to master.  Anywhere else it should go?


-- 
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=518002.



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

Message: 6
Date: Fri, 10 Jul 2009 10:14:16 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 518002] Custom Container example prints
        warnings on terminal
To: [email protected]
Message-ID: <[email protected]>
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=518002

  gtkmm | general | Ver: unspecified




------- Comment #4 from Jonathon Jongsma (jonner)  2009-07-10 10:14 UTC -------
yeah, the original fix was applied to gtkmm-2-12, so I manually applied it to
-14, -16, and master.  So I guess you need to apply your fix to -14 and -16 as
well (but only if we plan on making new releases of them I suppose)


-- 
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=518002.



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

Message: 7
Date: Fri, 10 Jul 2009 10:19:10 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[email protected]>
Subject: [gtkmm bugzilla] [Bug 518002] Custom Container example prints
        warnings on terminal
To: [email protected]
Message-ID: <[email protected]>
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=518002

  gtkmm | general | Ver: unspecified




------- Comment #5 from Murray Cumming  2009-07-10 10:19 UTC -------
We never know what we plan, so please someone commit any 2.12 fix to anything
newer than 2.12 too.


-- 
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=518002.



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

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge

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

_______________________________________________
Gtkmm-forge mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 38, Issue 2
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Reply via email to