GNOME.org
 

Gtkmm-forge Digest, Vol 20, Issue 7

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 433984]	Glib::ObjectBase::connect_property_changed
      doesn't return a	sigc::connection (glibmm (bugzilla.gnome.org))
   2. [Bug 495762] need get_pointer for RefPtr<>
      (glibmm (bugzilla.gnome.org))
   3. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   4. [Bug 511136] New: It's impossible to check if a	TreePath is
      valid using gtkmm functions (gtkmm (bugzilla.gnome.org))
   5. [Bug 511136] It's impossible to check if a	TreePath is valid
      using gtkmm functions (gtkmm (bugzilla.gnome.org))
   6. [Bug 505766] Gtk::RecentAction must derive from
      Gtk::RecentChooser (gtkmm (bugzilla.gnome.org))
   7. [Bug 511708] New: Gtkmm jhbuild error
      (glibmm (bugzilla.gnome.org))
   8. [Bug 511708] Gtkmm jhbuild error (glibmm (bugzilla.gnome.org))


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

Message: 1
Date: Sun, 20 Jan 2008 18:54:33 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 433984]
	Glib::ObjectBase::connect_property_changed doesn't return a
	sigc::connection
To: gtkmm-forge lists sourceforge net
Message-ID: <20080120185433 3951723F50B label 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=433984

  glibmm | object | Ver: 2.13.x

Murray Cumming changed:

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




------- Comment #5 from Murray Cumming  2008-01-20 18:54 UTC -------
I added a function rather than breaking the API even though the API is quite
new:

2008-01-20  Murray Cumming  <murrayc murrayc com>

        * glib/glibmm/objectbase.cc:
        * glib/glibmm/objectbase.h: Added
connect_property_changed_with_return() 
        because onnect_property_changed() doesn not return a sigc::connection.
        Bug #433984 (Philip Langdale, Kalle Vahlman).

Thank. Please do try using this.


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



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

Message: 2
Date: Sun, 20 Jan 2008 19:51:31 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 495762] need get_pointer for RefPtr<>
To: gtkmm-forge lists sourceforge net
Message-ID: <20080120195131 401B423F50A label 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=495762

  glibmm | general | Ver: 2.14.x




------- Comment #8 from Hubert Figuiere  2008-01-20 19:51 UTC -------
I don't agree with the necessity of preventing that. Actually I believe that it
should be allowed.


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



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

Message: 3
Date: Mon, 21 Jan 2008 00:10:50 +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: <20080121001050 D791523F5C8 label 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

chris cvine freeserve co uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chris cvine freeserve co uk




------- Comment #5 from chris cvine freeserve co uk  2008-01-21 00:10 UTC -------
On further thought, I think there may be a different difficulty with this
proposal, which is that sigc::trackable does not appear to be thread safe.

This problem arises where the slot to be executed represents a non-static
member function of a class object derived from sigc::trackable, and it arises
because the proposal would involve creating slot object(s) in one or more
worker threads, as well as executing the slots in a further different thread
(the Glib::MainContext thread) which eventually disposes of the slot, and each
act of creation and disposal appears to invoke sigc::trackable functions.  The
relevant Glib::MainContext thread is likely to be the thread which determines
the lifetime of that object, but there is a further vulnerability where that is
not the case.

I posted one solution to the original problem in this message:
http://mail.gnome.org/archives/gtkmm-list/2007-September/msg00009.html
but that seems to me to suffer from the same difficulty I have described above.

Glib::Dispatcher does not have these issues.  (It has slightly different issues
of a much lower importance.)

Chris


-- 
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: 4
Date: Mon, 21 Jan 2008 21:46:28 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 511136] New: It's impossible to check
	if a	TreePath is valid using gtkmm functions
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-511136-5595 http bugzilla 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=511136

  gtkmm | TreeView | Ver: 2.12.x
           Summary: It's impossible to check if a TreePath is valid using
                    gtkmm functions
           Product: gtkmm
           Version: 2.12.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Keywords: usability
          Severity: minor
          Priority: Normal
         Component: TreeView
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: ThJaeger gmail com
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: 2.19/2.20
   GNOME milestone: Unspecified


TreeView::get_cursor "returns" a TreePath, which according to the C
documentation, may be a NULL pointer (the gtkmm documenation is quiet about
this).  The only way to check if the path is valid that I can see is checking
if path.gobj() is valid, which is (i) ugly and (ii) undocumented.

My suggestion would be to implement
TreePath::operator bool () const {
    return gobj() != NULL;
}

or at least update the documentation to explain how the validity of a returned
TreePath can be checked.


The returned TreeViewColumn is probably affected as well.

Other information:


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



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

Message: 5
Date: Mon, 21 Jan 2008 21:47:26 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 511136] It's impossible to check if a
	TreePath is valid using gtkmm functions
To: gtkmm-forge lists sourceforge net
Message-ID: <20080121214726 CB3EC23F590 label 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=511136

  gtkmm | TreeView | Ver: 2.12.x

Tom Jaeger changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ThJaeger gmail com




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



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

Message: 6
Date: Tue, 22 Jan 2008 13:56:50 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 505766] Gtk::RecentAction must derive
	from	Gtk::RecentChooser
To: gtkmm-forge lists sourceforge net
Message-ID: <20080122135650 63A0F23F5C5 label 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=505766

  gtkmm | general | Ver: 2.12.x




------- Comment #4 from denes faluvegi hotmail com  2008-01-22 13:56 UTC -------
I tested gtkmm-2-12 branch, works as expected now, thank you.


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



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

Message: 7
Date: Thu, 24 Jan 2008 03:51:26 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 511708] New: Gtkmm jhbuild error
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-511708-5595 http bugzilla 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=511708

  glibmm | general | Ver: 2.4.x
           Summary: Gtkmm jhbuild error
           Product: glibmm
           Version: 2.4.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: general
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: jaalburqu svn gnome org
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: 2.19/2.20
   GNOME milestone: Unspecified


Please describe the problem:
When building gstreamermm with jhbuild, I ran into the following build error
for gtkmm and thought that it could be fixed by including a conversion to fix
it:

Making all in src
make[3]: Entering directory `/usr/src/jhbuild-sources/gtkmm/atk/src'
/opt/jhbuild-root/lib64/glibmm-2.4/proc/gmmproc -I ../../tools/m4 --defs .
action . ./../atkmm
No conversion from const gchar* to const Glib::ustring& defined (line: 0,
parameter name: desc)
m4 failed with exit code 1.  Aborting...
make[3]: *** [.stamps/stamp-action] Error 1

I included the conversion in glbmm/tools/m4/convert_glib.m4 because I thought
that it might be used elsewhere, but please feel free to move it elsewhere
(gtkmm/tools/m4/convert_atk.m4).

I also modified the file path in tests/giomm_simple/main.cc to be general in
testing giomm.  I hope these changes are useful.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:


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



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

Message: 8
Date: Thu, 24 Jan 2008 03:53:15 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 511708] Gtkmm jhbuild error
To: gtkmm-forge lists sourceforge net
Message-ID: <20080124035315 6CF1323F59C label 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=511708

  glibmm | general | Ver: 2.4.x




------- Comment #1 from Jos? Alburquerque  2008-01-24 03:53 UTC -------
Created an attachment (id=103608)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=103608&action=view)
Patch to fix gtkmm compile error


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



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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

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

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


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