GNOME.org
 

Gtkmm-forge Digest, Vol 11, Issue 6

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 339791] Gtk::Menu crash with child
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 350734] segfault in RadioAction constructor
      (gtkmm (bugzilla.gnome.org))
   3. [Bug 350734] segfault in RadioAction constructor
      (gtkmm (bugzilla.gnome.org))
   4. [Bug 429043] New: Encourage use of libglademm over	glade-- in
      the FAQ (gtkmm (bugzilla.gnome.org))
   5. [Bug 429043] Encourage use of libglademm over	glade-- in the
      FAQ (gtkmm (bugzilla.gnome.org))
   6. [Bug 339791] Gtk::Menu crash with child
      (gtkmm (bugzilla.gnome.org))
   7. [Bug 339791] Gtk::Menu crash with child
      (gtkmm (bugzilla.gnome.org))
   8. [Bug 339791] Gtk::Menu crash with child
      (gtkmm (bugzilla.gnome.org))


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

Message: 1
Date: Thu, 12 Apr 2007 12:17:37 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 339791] Gtk::Menu crash with child
To: gtkmm-forge lists sourceforge net
Message-ID: <20070412121737 724C16C41D7 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=339791

  gtkmm | general | Ver: 2.8.x

Johannes Schmid changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #86205|0                           |1
        is obsolete|                            |




------- Comment #29 from Johannes Schmid  2007-04-12 12:17 UTC -------
Created an attachment (id=86232)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=86232&action=view)
Patch to add a new special case for Gtk::Menu to
Widget_Class::dispose_vfunc_callback()

Tim Janik pointed out on gtk-devel-list that the behaviour in Gtk+ is correct
and consistent. At least it works like GtkContainer works but with the small
difference that gtk_menu_attach_to_widget cannot set widget->parent to the
widget it is attached to because it needs a GtkWindow as parent to be able to
popup.

So we need a new special case in Widget_Class::dispose_vfunc_callback to be
able to catch the Gtk::Menu case. I decided to use Widget_Class and not
Menu_Class because
a) I did not get it working correctly with Menu_Class
b) more important: Using Menu_Class might break ABI


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



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

Message: 2
Date: Thu, 12 Apr 2007 15:43:09 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 350734] segfault in RadioAction
	constructor
To: gtkmm-forge lists sourceforge net
Message-ID: <20070412154309 6AEE06C41B4 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=350734

  gtkmm | general | Ver: 2.9.x




------- Comment #3 from Armin Burgmeier  2007-04-12 15:43 UTC -------
Created an attachment (id=86241)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=86241&action=view)
Proposed patch

The problem lies within the changed signal of the radio action, which is
eventually emitted in the set_group() call. The code generated for the signal
contains a line that should invoke the C++ default signal handler and that
looks roughly like this:

obj->on_changed(Glib::wrap(p1));

where p1 is a GtkRadioAction*, in this case the same object as the object obj
wraps. Glib::wrap() creates a temporary Glib::RefPtr<Gtk::ActionGroup> that
decreases the reference count of p1 eventually without ever having refed it.
The patch now calls Glib::wrap(p1, true) to take an additional reference. It
also moves the conversion macro to radioaction.hg because other places might
need a conversion without an own reference (however, currently this is the only
place where such a conversion is ever required).

I wonder whether there are similar situations with other signals in gtkmm.


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



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

Message: 3
Date: Thu, 12 Apr 2007 15:47:20 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 350734] segfault in RadioAction
	constructor
To: gtkmm-forge lists sourceforge net
Message-ID: <20070412154720 6F4E96C41D3 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=350734

  gtkmm | general | Ver: 2.9.x

Armin Burgmeier changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |armin arbur net




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



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

Message: 4
Date: Thu, 12 Apr 2007 16:12:25 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 429043] New: Encourage use of
	libglademm over	glade-- in the FAQ
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-429043-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=429043

  gtkmm | documentation | Ver: 2.10.x
           Summary: Encourage use of libglademm over glade-- in the FAQ
           Product: gtkmm
           Version: 2.10.x
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: documentation
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: marko marko anastasov name
     GNOME version: Unspecified
   GNOME milestone: Unspecified


We often get questions about glademm on the list; I suppose that a lot of
people expect to have a GUI designer and some code generation. So I added some
explanation to clear things up a bit more.


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



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

Message: 5
Date: Thu, 12 Apr 2007 16:14:11 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 429043] Encourage use of libglademm
	over	glade-- in the FAQ
To: gtkmm-forge lists sourceforge net
Message-ID: <20070412161411 B93556C418D 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=429043

  gtkmm | documentation | Ver: 2.10.x




------- Comment #1 from Marko Anastasov  2007-04-12 16:14 UTC -------
Created an attachment (id=86243)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=86243&action=view)
gtkmm-faq.xml patch

Maybe we should also mention that gtkmm-list is for discussions about
libglademm and that glademm has its own?


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



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

Message: 6
Date: Thu, 12 Apr 2007 17:05:19 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 339791] Gtk::Menu crash with child
To: gtkmm-forge lists sourceforge net
Message-ID: <20070412170519 2FDF86C4190 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=339791

  gtkmm | general | Ver: 2.8.x




------- Comment #30 from Paul Davis  2007-04-12 17:05 UTC -------

else if (GTK_IS_MENU(pWidget) && gtk_menu_get_attach_widget(GTK_MENU(pWidget))
!= NULL)

Shouldn't we make this:

if( GTK_IS_MENU( pWidget ) && GTK_IS_MENU_ITEM( gtk_menu_get_attach_widget(
pWidget ) ) )


Granted I have no idea how robust GTK_IS_MENU_ITEM is to passing in NULL or
garbage pointers, but again, it seems like we should be testing for the
specific case of being attached to a MenuItem.

Also, in the source comment, you might want to add a line to the effect of:

Gtk::Menu does not use a parent widget because it must be contained in its
Gtk::Window so that it can be displayed as a Popup.

Other than that, I'm satisified.


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



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

Message: 7
Date: Fri, 13 Apr 2007 07:25:45 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 339791] Gtk::Menu crash with child
To: gtkmm-forge lists sourceforge net
Message-ID: <20070413072545 568A36C41CA 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=339791

  gtkmm | general | Ver: 2.8.x




------- Comment #31 from Johannes Schmid  2007-04-13 07:25 UTC -------
The question is what other widgets do with their menus. Usually they should
also destroy them for consistence with other GtkContainer-like widgets but I am
not sure that they do. Will it harm if we detach the menu before it is
destroyed?


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



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

Message: 8
Date: Fri, 13 Apr 2007 21:43:57 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 339791] Gtk::Menu crash with child
To: gtkmm-forge lists sourceforge net
Message-ID: <20070413214357 EF05E6C4197 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=339791

  gtkmm | general | Ver: 2.8.x




------- Comment #32 from Paul Davis  2007-04-13 21:43 UTC -------
I did a quick google through the gtk sources to see if there were any other
places where submenu's were getting destroyed.

grep "gtk_widget_destroy.*(.*submenu.*)" /usr/local/src/gnome/gtk+/gtk/*

And it only pulled up the line from gtkmenuitem.c so I think this is at least
some evidence that its the only place to worry about for now.

I'm not certain if it'd harm anything or not. I do know that we know that we
want to detach non-managed widgets from menuitems, and without any idea on what
happens anywhere else, I would feel most comfortable making this patch as
specific to this case as possible.  Then if we find in the future that there
are other corner casese, we can relax this patch to include those cases as
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=339791.



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

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

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


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