[gtkmm] Gtkmm-forge digest, Vol 1 #211 - 15 msgs
- From: gtkmm-forge-request lists sourceforge net
- To: gtkmm-forge lists sourceforge net
- Subject: [gtkmm] Gtkmm-forge digest, Vol 1 #211 - 15 msgs
- Date: Thu, 29 Aug 2002 04:14:05 -0700
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.
Today's Topics:
1. [Bug 91614] Changed - back patch for enum operator overloading (bugzilla-daemon widget gnome org)
2. [Bug 91614] Changed - back patch for enum operator overloading (bugzilla-daemon widget gnome org)
3. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
4. [Bug 91410] Changed - Gtk::Menu not properly C++ wrapped (bugzilla-daemon widget gnome org)
5. [Bug 91922] New - No way to get default Gdk::Cursor (bugzilla-daemon widget gnome org)
6. [Bug 79332] Changed - Can't autogen.sh gtkmm_hello (bugzilla-daemon widget gnome org)
7. [Bug 91922] Changed - No way to get default Gdk::Cursor (bugzilla-daemon widget gnome org)
8. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
9. [Bug 91614] Changed - back patch for enum operator overloading (bugzilla-daemon widget gnome org)
10. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
11. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
12. [Bug 91410] Changed - Gtk::Menu not properly C++ wrapped (bugzilla-daemon widget gnome org)
13. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
14. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
15. [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor. (bugzilla-daemon widget gnome org)
--__--__--
Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc:
Date: Wed, 28 Aug 2002 15:24:26 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91614] Changed - back patch for enum operator overloading
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91614
Changed by szombath bifab de
--- shadow/91614 Wed Aug 28 07:00:24 2002
+++ shadow/91614.tmp.13344 Wed Aug 28 15:24:26 2002
@@ -70,6 +70,11 @@
see URLs to your bugzilla bugs that show that they are necessary. I
think some people will not install the patches until they see the
errors, so it's nice to see the solution to those errors.
------- Additional Comments From murrayc usa net 2002-08-28 07:00 -------
Applied patch 10697 because people need to apply some SUN patches anyway.
+
+------- Additional Comments From szombath bifab de 2002-08-28 15:24 -------
+Created an attachment (id=10773)
+REDAME.sun, some correction made as proposed
+
--__--__--
Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc:
Date: Wed, 28 Aug 2002 15:44:43 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91614] Changed - back patch for enum operator overloading
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91614
Changed by szombath bifab de
--- shadow/91614 Wed Aug 28 15:24:26 2002
+++ shadow/91614.tmp.16331 Wed Aug 28 15:44:43 2002
@@ -75,6 +75,34 @@
Applied patch 10697 because people need to apply some SUN patches anyway.
------- Additional Comments From szombath bifab de 2002-08-28 15:24 -------
Created an attachment (id=10773)
REDAME.sun, some correction made as proposed
+
+------- Additional Comments From szombath bifab de 2002-08-28 15:44 -------
+> README.SUN:
+> - autoconf and automake should not be required for building gtkmm,
+> unless building from cvs.
+
+Both removed from requirements.
+
+> - gtkmm should never be called "Gtk--".
+
+Changed. I did'nt know about this.
+
+> - Is there a URL that shows the patch(es), with descriptions of the
+> problems that they fix? If not, then people might at least like to
+> see URLs to your bugzilla bugs that show that they are necessary. I
+> think some people will not install the patches until they see the
+> errors, so it's nice to see the solution to those errors.
+
+Well, the URL I gave is the entry point to get all of the compiler
+patches. All patches come with descriptions which mention the bug id's
+they resolve, But the bug descriptions itself are not available.
+
+I really disagree with you at the point to make all requirements
+transparent to the Forte C++ users. I think it is enough to describe a
+reasonable setup which works for gtkmm. The commercial UNIX field is
+somewhat different from the Open Source OS's. Companies used to have
+support from their vendors or hire staff for solving software problems.
+
--__--__--
Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: harald hopfes hopfes sysde eads net, szombath bifab de
Date: Wed, 28 Aug 2002 15:45:07 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by mhl schulze t-online de
--- shadow/78578 Wed Aug 28 14:56:06 2002
+++ shadow/78578.tmp.16566 Wed Aug 28 15:45:07 2002
@@ -408,6 +408,19 @@
For, now the workaround would be to use the default constructor and
add the child widget manually in your own constructor.
------- Additional Comments From madmaxer poczta fm 2002-08-28 14:56 -------
I checked this problem with g++-3.2, gtkmm 1.3.21, libsigc++ 1.1.13 and the test proggy did not crash. It seems to be a compiler problem.
+
+------- Additional Comments From MHL Schulze t-online de 2002-08-28 15:45 -------
+I experience the segfault with gcc 2.95.3. Me too, I get stuck during
+the dynamic cast in Gtk::Container_Class::add_callback(). However the
+argument passed to dynamic_cast() is 0x1. Stepping through the code
+_before_ the segfault happens, I find that our instantiation of the
+class NewNodeMenuItem retrieved with g_object_get_qdata(object,
+Glib::quark_) in ObjectBase::_get_current_wrapper(object) seems to be
+corrupted. E.g. the data member SigC::ObejctBase::control_ suddenly is
+non-zero and points to some undefined piece of memory. During
+initialization of the wrapper I can't see anything abnormal. All data
+seems perfectly valid when stored with g_object_set_qdata_full() in
+ObjectBase::_set_current_wrapper().
--__--__--
Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc:
Date: Wed, 28 Aug 2002 16:13:42 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91410] Changed - Gtk::Menu not properly C++ wrapped
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91410
Changed by szombath bifab de
--- shadow/91410 Wed Aug 28 07:06:57 2002
+++ shadow/91410.tmp.653 Wed Aug 28 16:13:42 2002
@@ -97,6 +97,51 @@
GTK+ examples, but not he gtkmm example.
------- Additional Comments From murrayc usa net 2002-08-28 07:06 -------
I'd like to fix this properly, but is it a memory leak if you don't
call list_toplevels()?
+
+------- Additional Comments From szombath bifab de 2002-08-28 16:13 -------
+No, the memory leak is introduced by calling Window_Class::wrap_new()
+for an unrelated gtk+ object, which occured during the list iteration
+in toplevel_window().
+
+Here the purify output:
+ PLK: 36 bytes potentially leaked at 0x12ef70
+ This memory was allocated from:
+ malloc [rtlib.o]
+ c2n6Fi_Pv___1 [libCrun.so.1]
+ void*operator new(unsigned) [rtlib.o]
+ Glib::ObjectBase*Gtk::Window_Class::wrap_new(_GObject*)
+[window.cc:487]
+
+ Glib::ObjectBase* Window_Class::wrap_new(GObject* o)
+ {
+ => return new Window((GtkWindow*)(o)); //top-level
+windows can not be manage()ed.
+
+ }
+
+
+Glib::ObjectBase*__unnamed_kJQAKcVNb9wkv::create_new_wrapper(_GObject*)
+[wrap.cc:71]
+ if(const gpointer idx = g_type_get_qdata(type,
+Glib::quark_))
+ {
+ const Glib::WrapNewFunction func =
+(*wrap_func_table)[GPOINTER_TO_UINT(idx)];
+ => return (*func)(object);
+ }
+ }
+
+ Glib::ObjectBase*Glib::wrap_auto(_GObject*,bool)
+[wrap.cc:138]
+ if(!pCppObject)
+ {
+ // There's not already a wrapper: generate a new
+C++ instance.
+ => pCppObject = create_new_wrapper(object);
+
+ if(!pCppObject)
+ {
+
--__--__--
Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc:
Date: Wed, 28 Aug 2002 18:31:36 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91922] New - No way to get default Gdk::Cursor
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91922
Changed by cactus cactus rulez org
--- shadow/91922 Wed Aug 28 18:31:36 2002
+++ shadow/91922.tmp.5834 Wed Aug 28 18:31:36 2002
@@ -0,0 +1,22 @@
+Bug#: 91922
+Product: gtkmm
+Version: 2.0
+OS: other
+OS Details:
+Status: NEW
+Resolution:
+Severity: normal
+Priority: Normal
+Component: general
+AssignedTo: gtkmm-forge lists sourceforge net
+ReportedBy: cactus cactus rulez org
+TargetMilestone: ---
+URL:
+Summary: No way to get default Gdk::Cursor
+
+Some methods (like gdk_window_set_cursor and gnome_canvas_item_grab) use 0
+for their GdkCursor* argument to indicate a (re)setting of the default
+cursor. There's no way to get this cursor with Gdkmm.
+
+One possibility would be a static get_default() method in Gdk::Cursor that
+returned some special Gdk::Cursor that returns 0 in gobj()
--__--__--
Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, murrayc usa net
Cc:
Date: Wed, 28 Aug 2002 19:06:54 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 79332] Changed - Can't autogen.sh gtkmm_hello
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=79332
Changed by kenneth gnu org
--- shadow/79332 Sat Jun 22 11:21:46 2002
+++ shadow/79332.tmp.12238 Wed Aug 28 19:06:53 2002
@@ -9,13 +9,12 @@
Priority: Normal
Component: build
AssignedTo: gtkmm-forge lists sourceforge net
ReportedBy: murrayc usa net
TargetMilestone: ---
URL:
-Cc:
Summary: Can't autogen.sh gtkmm_hello
BugsThisDependsOn: 71678
When running autogen.sh in gnomemm/gtkmm_hello, with a
vicious-build-scripts head setup:
--__--__--
Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, cactus cactus rulez org
Cc:
Date: Thu, 29 Aug 2002 04:16:51 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91922] Changed - No way to get default Gdk::Cursor
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91922
Changed by murrayc usa net
--- shadow/91922 Wed Aug 28 18:31:36 2002
+++ shadow/91922.tmp.22091 Thu Aug 29 04:16:51 2002
@@ -17,6 +17,17 @@
Some methods (like gdk_window_set_cursor and gnome_canvas_item_grab) use 0
for their GdkCursor* argument to indicate a (re)setting of the default
cursor. There's no way to get this cursor with Gdkmm.
One possibility would be a static get_default() method in Gdk::Cursor that
returned some special Gdk::Cursor that returns 0 in gobj()
+
+------- Additional Comments From murrayc usa net 2002-08-29 04:16 -------
+It's really the "parent's cursor" rather than the "default cursor".
+I'm not sure that I want a
+Gtk::Cursor(bool
+use_the_parents_cursors_whenever_this_gtkmmcursor_is_used)
+constructor.
+
+Both Gdk::Window::set_cursor() and Gnome::Canvas::Item::grab() already
+have overloads that allow the use of the parent's cursor instead of
+specifying one.
--__--__--
Message: 8
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: harald hopfes hopfes sysde eads net, szombath bifab de
Date: Thu, 29 Aug 2002 04:19:07 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by murrayc usa net
--- shadow/78578 Wed Aug 28 15:45:07 2002
+++ shadow/78578.tmp.22426 Thu Aug 29 04:19:07 2002
@@ -421,6 +421,15 @@
Glib::quark_) in ObjectBase::_get_current_wrapper(object) seems to be
corrupted. E.g. the data member SigC::ObejctBase::control_ suddenly is
non-zero and points to some undefined piece of memory. During
initialization of the wrapper I can't see anything abnormal. All data
seems perfectly valid when stored with g_object_set_qdata_full() in
ObjectBase::_set_current_wrapper().
+
+------- Additional Comments From murrayc usa net 2002-08-29 04:19 -------
+Martin, I find that debuggers and printf give me a variety of
+different values for the pointers. Basically, that memory is corrupted.
+
+I remember Karl Nelson talking about a gcc bug that prevented use of
+dynamic_cast in either constructors or destructors. This looks like
+exactly that. It seems to be fixed in later versions of gcc, and there
+are workarounds for older compilers, so I'm thinking of closing this bug.
--__--__--
Message: 9
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc:
Date: Thu, 29 Aug 2002 04:24:14 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91614] Changed - back patch for enum operator overloading
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91614
Changed by murrayc usa net
--- shadow/91614 Wed Aug 28 15:44:43 2002
+++ shadow/91614.tmp.23461 Thu Aug 29 04:24:14 2002
@@ -1,13 +1,13 @@
Bug#: 91614
Product: gtkmm
Version: 2.0
OS: SunOS
OS Details:
-Status: NEW
-Resolution:
+Status: RESOLVED
+Resolution: FIXED
Severity: normal
Priority: Normal
Component: build
AssignedTo: gtkmm-forge lists sourceforge net
ReportedBy: szombath bifab de
TargetMilestone: ---
@@ -103,6 +103,15 @@
I really disagree with you at the point to make all requirements
transparent to the Forte C++ users. I think it is enough to describe a
reasonable setup which works for gtkmm. The commercial UNIX field is
somewhat different from the Open Source OS's. Companies used to have
support from their vendors or hire staff for solving software problems.
+
+------- Additional Comments From murrayc usa net 2002-08-29 04:24 -------
+Yes, if they need to apply some patches then they might as well apply
+all patches. But in general I think it is optimistic to expect people
+to read our documentation. In case they don't read it, I like to make
+sure that they find the answers to the problems that they will then
+encounter.
+
+README.SUN added. Thanks.
--__--__--
Message: 10
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: szombath bifab de
Date: Thu, 29 Aug 2002 04:51:57 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by harald hopfes hopfes sysde eads net
--- shadow/78578 Thu Aug 29 04:19:07 2002
+++ shadow/78578.tmp.27995 Thu Aug 29 04:51:57 2002
@@ -430,6 +430,9 @@
different values for the pointers. Basically, that memory is corrupted.
I remember Karl Nelson talking about a gcc bug that prevented use of
dynamic_cast in either constructors or destructors. This looks like
exactly that. It seems to be fixed in later versions of gcc, and there
are workarounds for older compilers, so I'm thinking of closing this bug.
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2002-08-29 04:51 -------
+Does that mean, you will include a workaround inside gtkmm?
--__--__--
Message: 11
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: harald hopfes hopfes sysde eads net, szombath bifab de
Date: Thu, 29 Aug 2002 05:32:04 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by murrayc usa net
--- shadow/78578 Thu Aug 29 04:51:57 2002
+++ shadow/78578.tmp.3026 Thu Aug 29 05:32:04 2002
@@ -433,6 +433,11 @@
dynamic_cast in either constructors or destructors. This looks like
exactly that. It seems to be fixed in later versions of gcc, and there
are workarounds for older compilers, so I'm thinking of closing this bug.
------- Additional Comments From harald hopfes hopfes sysde eads net 2002-08-29 04:51 -------
Does that mean, you will include a workaround inside gtkmm?
+
+------- Additional Comments From murrayc usa net 2002-08-29 05:32 -------
+You already have workarounds - use different constructors. I don't see
+how to workaround it inside gtkmm, but I would look at any patch that
+you give us.
--__--__--
Message: 12
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc:
Date: Thu, 29 Aug 2002 05:48:00 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91410] Changed - Gtk::Menu not properly C++ wrapped
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91410
Changed by murrayc usa net
--- shadow/91410 Wed Aug 28 16:13:42 2002
+++ shadow/91410.tmp.5342 Thu Aug 29 05:48:00 2002
@@ -142,6 +142,10 @@
C++ instance.
=> pCppObject = create_new_wrapper(object);
if(!pCppObject)
{
+
+------- Additional Comments From murrayc usa net 2002-08-29 05:47 -------
+So this isn't a very high priority because that method isn't used very
+much.
--__--__--
Message: 13
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: harald hopfes hopfes sysde eads net, szombath bifab de
Date: Thu, 29 Aug 2002 06:06:21 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by andreas holzmann epost de
--- shadow/78578 Thu Aug 29 05:32:04 2002
+++ shadow/78578.tmp.8931 Thu Aug 29 06:06:20 2002
@@ -438,6 +438,17 @@
Does that mean, you will include a workaround inside gtkmm?
------- Additional Comments From murrayc usa net 2002-08-29 05:32 -------
You already have workarounds - use different constructors. I don't see
how to workaround it inside gtkmm, but I would look at any patch that
you give us.
+
+------- Additional Comments From Andreas Holzmann epost de 2002-08-29 06:06 -------
+As others already said the problem seems to occur in Gtk::Container.
+It seems that you get the segmentation faults whenever you extend
+a class that is derived from Gtk::Container. I got this because
+I have extended Gtk::Window (gcc 2.95). The symptoms are the same as
+described by Martin Schulze when I add a Gtk::VBox inside my constructor.
+It seems to be a compiler problem because I don't have these problems
+when I use gcc 3.0 or gcc 3.2.
+Maybe we should add a comment to the system requirements of the gtkmm
+library that users should use a gcc version > 2.95?
--__--__--
Message: 14
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: szombath bifab de
Date: Thu, 29 Aug 2002 06:32:25 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by harald hopfes hopfes sysde eads net
--- shadow/78578 Thu Aug 29 06:06:20 2002
+++ shadow/78578.tmp.13881 Thu Aug 29 06:32:25 2002
@@ -449,6 +449,13 @@
I have extended Gtk::Window (gcc 2.95). The symptoms are the same as
described by Martin Schulze when I add a Gtk::VBox inside my constructor.
It seems to be a compiler problem because I don't have these problems
when I use gcc 3.0 or gcc 3.2.
Maybe we should add a comment to the system requirements of the gtkmm
library that users should use a gcc version > 2.95?
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2002-08-29 06:32 -------
+> Maybe we should add a comment to the system requirements of the
+> gtkmm library that users should use a gcc version > 2.95?
+
+That would be wise!
+
--__--__--
Message: 15
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: harald hopfes hopfes sysde eads net, szombath bifab de
Date: Thu, 29 Aug 2002 07:13:43 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 78578] Changed - Segfault when calling the MenuItem superconstructor.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=78578
Changed by murrayc usa net
--- shadow/78578 Thu Aug 29 06:32:25 2002
+++ shadow/78578.tmp.22901 Thu Aug 29 07:13:43 2002
@@ -456,6 +456,19 @@
------- Additional Comments From harald hopfes hopfes sysde eads net 2002-08-29 06:32 -------
> Maybe we should add a comment to the system requirements of the
> gtkmm library that users should use a gcc version > 2.95?
That would be wise!
+
+------- Additional Comments From murrayc usa net 2002-08-29 07:13 -------
+Andreas, I only expect you to have this problem when you use a
+constructor that adds a child widget, not when you use _any_
+constructor. If you think that it is impossible to derive from any
+Container then please give me test code. I really doubt it because
+there are lots of classes that derive from Container and they work
+fine.
+
+Yes, we do need to put this in the FAQ. We would tell people to use
+the workaround or upgrade their compiler if they find this problem. A
+later gcc is _not_ a requirement for gtkmm, because people don't
+_need_ to use those convenience constructors.
--__--__--
_______________________________________________
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]
