GNOME.org
 

Gtkmm-forge digest, Vol 1 #1012 - 10 msgs

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-admin 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 321552] Double entries in trackable list when binding a slot to a slot (libsigc++ (bugzilla.gnome.org))
   2. [Bug 321552] Double entries in trackable list when binding a slot to a slot (libsigc++ (bugzilla.gnome.org))
   3. [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals. (gtkmm (bugzilla.gnome.org))
   4. [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals. (gtkmm (bugzilla.gnome.org))
   5. [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals. (gtkmm (bugzilla.gnome.org))
   6. [Bug 315874] GObject wrapper is considered destroyed too soon (glibmm (bugzilla.gnome.org))
   7. [Bug 315874] GObject wrapper is considered destroyed too soon (glibmm (bugzilla.gnome.org))
   8. [Bug 315874] GObject wrapper is considered destroyed too soon (glibmm (bugzilla.gnome.org))
   9. [Bug 315874] GObject wrapper is considered destroyed too soon (glibmm (bugzilla.gnome.org))
  10. [Bug 321552] Double entries in trackable list when binding a slot to a slot (libsigc++ (bugzilla.gnome.org))

--__--__--

Message: 1
From: "libsigc++ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 03:29:00 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321552] Double entries in trackable list when binding a slot to a slot

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321552
 libsigc++ | adaptors | Ver: 2.0.x





------- Additional Comments From Murray Cumming  2005-12-02 08:28 -------
> The implication then seems to be that it's a g++ error that has since b=
een
fixed.

I wouldn't rely on that. Could you upload the valgrind output, even if it=
 isn't
completely useful, please? If we can reproduce the problem then surely we=
 should
be able to discover when/how it is happening.

Slots as bound slot parameters: You really are exercising the API.



------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 2
From: "libsigc++ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 03:29:30 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321552] Double entries in trackable list when binding a slot to a slot

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321552
 libsigc++ | adaptors | Ver: 2.0.x

Murray Cumming changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
             Status|RESOLVED                    |REOPENED
         Resolution|NOTGNOME                    |



------- Additional Comments From Murray Cumming  2005-12-02 08:29 -------
Reopening, just in case.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 3
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 06:50:30 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals.

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D172345
 gtkmm | general | Ver: 2.6.x

Murray Cumming changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
  BugsThisDependsOn|                            |323007



------- Additional Comments From Murray Cumming  2005-12-02 11:50 -------
I tried to implement set_current_value in gtkmm (see patch), but there is=
 no
public GTK+ API to get the GtkActionGroup from the GtkRadioAction/GtkActi=
on. I
requested an implementation in GTK+ in bug #323007.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 4
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 06:52:08 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals.

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D172345
 gtkmm | general | Ver: 2.6.x





------- Additional Comments From Murray Cumming  2005-12-02 11:52 -------
Created an attachment (id=3D55518)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=3D55518&action=3Dview)
radio_action_set_current_value.patch

Unfinished patch.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 5
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 07:32:49 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 172345] Gtk::RadioAction, unable to specifiy initial activated entry without emitting signals.

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D172345
 gtkmm | general | Ver: 2.6.x





------- Additional Comments From Murray Cumming  2005-12-02 12:32 -------
> With the C interface you can set the default action
> without activating anything. If you activate the action the attached si=
gnals are
> called out thus doing something that normally only the user initiate.

gtk_action_group_add_radio_action() does this by activating the action be=
fore
connecting the signal. You can do that too in the C++ API, by calling
RadioAction::set_active() before calling ActionGroup::add(action, *).=20


Maybe it would help to add a bool active parameter to RadioAction::create=
(), but
it already has lots of parameters.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 6
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 09:19:35 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 315874] GObject wrapper is considered destroyed too soon

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D315874
 glibmm | object | Ver: 2.8.x





------- Additional Comments From Murray Cumming  2005-12-02 14:19 -------
Confirmed. When closing the window, I get:

(a.out:29961): glibmm-WARNING **: Glib::create_new_wrapper: Attempted to =
create
a 2nd C++ wrapper for a C instance whose C++ wrapper has been deleted.

(a.out:29961): glibmm-WARNING **: failed to wrap type of 'gtkmm__GtkVBox'
Child removed



------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 7
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 09:29:48 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 315874] GObject wrapper is considered destroyed too soon

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D315874
 glibmm | object | Ver: 2.8.x





------- Additional Comments From Murray Cumming  2005-12-02 14:29 -------
The backtrace with --g-fatal-warnings:

#0  IA__g_logv (log_domain=3D<value optimized out>, log_level=3DG_LOG_LEV=
EL_WARNING,
    format=3D0xb790dba0 "Glib::create_new_wrapper: Attempted to create a =
2nd C++
wrapper for a C instance whose C++ wrapper has been deleted.", args1=3D0x=
bfe3a40c
"\001") at gmessages.c:503
#1  0xb766f82e in IA__g_log (log_domain=3D0xb790b991 "glibmm",
log_level=3DG_LOG_LEVEL_WARNING,
    format=3D0xb790dba0 "Glib::create_new_wrapper: Attempted to create a =
2nd C++
wrapper for a C instance whose C++ wrapper has been deleted.") at gmessag=
es.c:517
#2  0xb790b385 in create_new_wrapper (object=3D0x80a5788) at wrap.cc:56
#3  0xb790b4b5 in Glib::wrap_auto (object=3D0x80a5788, take_copy=3Dfalse)=
 at wrap.cc:138
#4  0xb7e5ff72 in Glib::wrap (object=3D0x80a5788, take_copy=3Dfalse) at w=
idget.cc:2832
#5  0xb7de0333 in (anonymous namespace)::Container_signal_remove_callback
(self=3D0x809c588, p0=3D0x80a5788,
    data=3D0x80a5730) at container.cc:210
#6  0xb76e501d in IA__g_cclosure_marshal_VOID__OBJECT (closure=3D0x80a58d=
8,
return_value=3D0x0, n_param_values=3D2,
    param_values=3D0xbfe3a72c, invocation_hint=3D0xbfe3a63c,
marshal_data=3D0xb7de02f0) at gmarshal.c:636
#7  0xb76d706b in IA__g_closure_invoke (closure=3D0x80a58d8, return_value=
=3D0x0,
n_param_values=3D2,
    param_values=3D0xbfe3a72c, invocation_hint=3D0xbfe3a63c) at gclosure.=
c:490
#8  0xb76e81e8 in signal_emit_unlocked_R (node=3D0x80976f8, detail=3D0,
instance=3D0x809c588, emission_return=3D0x0,
    instance_and_params=3D0xbfe3a72c) at gsignal.c:2519
#9  0xb76e9417 in IA__g_signal_emit_valist (instance=3D0x809c588, signal_=
id=3D70,
detail=3D0,
    var_args=3D<value optimized out>) at gsignal.c:2208
#10 0xb76e97ae in IA__g_signal_emit (instance=3D0x809c588, signal_id=3D70=
, detail=3D0)
at gsignal.c:2252
#11 0xb79ccc60 in IA__gtk_container_remove (container=3D0x809c588,
widget=3D0x80a5788) at gtkcontainer.c:995
#12 0xb7b3f645 in gtk_widget_dispose (object=3D0x80a5788) at gtkwidget.c:=
6648
#13 0xb7e640a7 in Gtk::Widget_Class::dispose_vfunc_callback (self=3D0x80a=
5788) at
widget.cc:508
#14 0xb76da76d in IA__g_object_run_dispose (object=3D0x80a5788) at gobjec=
t.c:569
---Type <return> to continue, or q <return> to quit---
#15 0xb7a71c4f in IA__gtk_object_destroy (object=3D0x80a5788) at gtkobjec=
t.c:363
#16 0xb7e1293d in Gtk::Object::_destroy_c_instance (this=3D0xbfe3ab50) at
object.cc:166
#17 0xb7e12a5d in Gtk::Object::destroy_ (this=3D0xb7536938) at object.cc:=
264
#18 0xb7dc742a in ~VBox (this=3D0xbfe3ab50) at box.cc:461
#19 0x0804c712 in MyWindow::~MyWindow ()
#20 0x0804c272 in main ()


------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 8
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 09:41:15 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 315874] GObject wrapper is considered destroyed too soon

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D315874
 glibmm | object | Ver: 2.8.x





------- Additional Comments From Murray Cumming  2005-12-02 14:41 -------
Here's one of my (usually wrong) ideas:
Maybe Container_signal_remove_callback() (the C callbacks that call the
connected handler slots when a signal is emitted) should do the same clev=
er
things that Container_Class::remove_callback_custom() (The default signal
handler) does. I guess that the signal handlers are called before the def=
ault
signal handler, and this cleverness should happen as soon as possible. Th=
is
could stop the warning, at least, though I don't think the handler would =
be called.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 9
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 09:57:32 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 315874] GObject wrapper is considered destroyed too soon

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D315874
 glibmm | object | Ver: 2.8.x





------- Additional Comments From Murray Cumming  2005-12-02 14:57 -------
And I guess that you connected to the signal because you noticed that an
on_remove() override was being not called.

> it's perfectly valid to listen for the remove signal and to be notified=
 at
delete time

If possible, I'd like to make that work, though preventing crashes would =
be a
priority if I have to choose.


------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 10
From: "libsigc++ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri,  2 Dec 2005 15:04:25 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321552] Double entries in trackable list when binding a slot to a slot

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321552
 libsigc++ | adaptors | Ver: 2.0.x





------- Additional Comments From Philip Langdale  2005-12-02 20:04 ------=
-
Created an attachment (id=3D55549)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=3D55549&action=3Dview)
Valgrind log output

As requested.

------- You are receiving this mail because: -------
You are the assignee for the bug.



--__--__--

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


End of Gtkmm-forge Digest
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]