Gtkmm-forge Digest, Vol 34, Issue 14



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 575268] Gtk::StatusIcon::get_geometry cause	crashes
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 575268] Gtk::StatusIcon::get_geometry cause	crashes
      (gtkmm (bugzilla.gnome.org))
   3. [Bug 575268] Gtk::StatusIcon::get_geometry cause	crashes
      (gtkmm (bugzilla.gnome.org))
   4. [Bug 574844] gstreamermm build broken in example
      (gnomemm (bugzilla.gnome.org))
   5. [Bug 575142] clutter-gtkmm: Unable to make the	stage window
      0x240001f the current GLX drawable (gnomemm (bugzilla.gnome.org))
   6. [Bug 575533] New: Wrap	g_object_freeze_notify/thaw_notify()
      (glibmm (bugzilla.gnome.org))
   7. [Bug 573482] libglademm: thoughts about signal	autoconnecting
      (gtkmm (bugzilla.gnome.org))
   8. [Bug 573482] libglademm: thoughts about signal	autoconnecting
      (gtkmm (bugzilla.gnome.org))


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

Message: 1
Date: Fri, 13 Mar 2009 16:59:59 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 575268] Gtk::StatusIcon::get_geometry
	cause	crashes
To: gtkmm-forge lists sourceforge net
Message-ID: <20090313165959 3FBBC23F52E 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=575268

  gtkmm | general | Ver: 2.15.x




------- Comment #1 from Hubert Figuiere  2009-03-13 17:00 UTC -------
Created an attachment (id=130589)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=130589&action=view)
sample code

Compile with g++ gtkmmbug.cc -o gtkmmbug `pkg-config --cflags --libs gtkmm-2.4`


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



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

Message: 2
Date: Fri, 13 Mar 2009 17:01:20 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 575268] Gtk::StatusIcon::get_geometry
	cause	crashes
To: gtkmm-forge lists sourceforge net
Message-ID: <20090313170120 D29D323F526 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=575268

  gtkmm | general | Ver: 2.15.x




------- Comment #2 from Hubert Figuiere  2009-03-13 17:01 UTC -------
I use gtkmm2-2.15.5


Also if I use the plain C API it does not crash.


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



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

Message: 3
Date: Fri, 13 Mar 2009 17:08:41 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 575268] Gtk::StatusIcon::get_geometry
	cause	crashes
To: gtkmm-forge lists sourceforge net
Message-ID: <20090313170841 91A5523F544 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=575268

  gtkmm | general | Ver: 2.15.x

Murray Cumming changed:

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




------- Comment #3 from Murray Cumming  2009-03-13 17:08 UTC -------
I guess the screen output parameter is just missing a reference.


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



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

Message: 4
Date: Fri, 13 Mar 2009 18:39:54 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 574844] gstreamermm build broken in
	example
To: gtkmm-forge lists sourceforge net
Message-ID: <20090313183954 C92B323F52E 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=574844

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #11 from Jos? Alburquerque  2009-03-13 18:39 UTC -------
Also, my Spanish should have helped me because it is written (and pronounced as
written) 'existencia'.  If I had taken the time to repeat the word in Spanish I
might have known that the second 'e' is also used in English and not an 'a'.
:-)


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



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

Message: 5
Date: Sat, 14 Mar 2009 19:09:47 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 575142] clutter-gtkmm: Unable to make
	the	stage window 0x240001f the current GLX drawable
To: gtkmm-forge lists sourceforge net
Message-ID: <20090314190947 66F4223F52E 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=575142

  gnomemm | cluttermm | Ver: unspecified




------- Comment #1 from Maurice van der Pot  2009-03-14 19:09 UTC -------
I've asked two other people to try out the same application and it reported the
same failure for them.

glXMakeCurrent seems to fail with error 10 (BadAccess). The docs say:

  BadAccess is generated if ctx was current to another thread at the time
glXMakeCurrent was called.

I have no clue why this is happening.


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



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

Message: 6
Date: Mon, 16 Mar 2009 09:36:59 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 575533] New: Wrap
	g_object_freeze_notify/thaw_notify()
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-575533-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=575533

  glibmm | general | Ver: unspecified
           Summary: Wrap g_object_freeze_notify/thaw_notify()
           Product: glibmm
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: general
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: murrayc murrayc com
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


We should wrap these functions:
http://library.gnome.org/devel/gobject/unstable/gobject-The-Base-Object-Type.html#g-object-freeze-notify
which are mentioned, for instance in the Gtk:::Adjustment documentation:
http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/classGtk_1_1Adjustment.html#8b64cd68e91a24d6b7dfc03d8d199437


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



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

Message: 7
Date: Mon, 16 Mar 2009 13:35:48 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 573482] libglademm: thoughts about
	signal	autoconnecting
To: gtkmm-forge lists sourceforge net
Message-ID: <20090316133548 2B2BB23F536 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=573482

  gtkmm | general | Ver: unspecified




------- Comment #32 from Murray Cumming  2009-03-16 13:36 UTC -------
Note to self: If I implement the signal registration system that would be
needed to make this work, I would want that registration to only happen just
before it is actually used, to avoid unnecessary slowdowns during normal gtkmm
initialization.


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



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

Message: 8
Date: Mon, 16 Mar 2009 13:34:32 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 573482] libglademm: thoughts about
	signal	autoconnecting
To: gtkmm-forge lists sourceforge net
Message-ID: <20090316133432 E0D0D23F536 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=573482

  gtkmm | general | Ver: unspecified




------- Comment #31 from Murray Cumming  2009-03-16 13:34 UTC -------
About example.patch, aren't these in the wrong order? Doesn't the signal
handler need to be declared _before_ you use it?

class MySlots : public Glib::SlotsContainer
{
private:
 GTKBUILDER_DECLARE_SLOTS(
  GTKBUILDER_SLOT(MySlots, on_button_clicked)
);

void on_button_clicked()
{
  if(pDialog)
    pDialog->hide(); //hide() will cause main::run() to end.
}

Also, I would really really like to avoid use of macros at least in the public
API. Can you try that, please?


And I unfortunately still don't find this much nicer than connecting manually.
It only saves me from having to remember the names of the signals that I am
connecting to, though
a) that's usually fairly obvious from my signal handler names.
b) I still need to remember what parameters the signal handlers take, which I
can only know if I know the signal names.


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



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

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com

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

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


End of Gtkmm-forge Digest, Vol 34, Issue 14
*******************************************


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]