GNOME.org
 

[gtkmm] Gtkmm-forge digest, Vol 1 #186 - 7 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.


Today's Topics:

   1. [Bug 90095] Changed - Errors to stderr when running libglademm/examples/variablesmap (bugzilla-daemon widget gnome org)
   2. [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19 (bugzilla-daemon widget gnome org)
   3. [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19 (bugzilla-daemon widget gnome org)
   4. [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19 (bugzilla-daemon widget gnome org)
   5. [Bug 89951] Changed - gtkmm cvs doesn't compile with gcc 2.95.3 due to internal compiler error (bugzilla-daemon widget gnome org)
   6. [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19 (bugzilla-daemon widget gnome org)
   7. [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19 (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, michael koziarski com
Cc: 
Date: Thu,  8 Aug 2002 10:11:39 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90095] Changed - Errors to stderr when running libglademm/examples/variablesmap

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=90095

Changed by murrayc usa net 

--- shadow/90095	Wed Aug  7 17:10:27 2002
+++ shadow/90095.tmp.25782	Thu Aug  8 10:11:39 2002
@@ -1,12 +1,12 @@
 Bug#: 90095
 Product: gnomemm
 Version: 2.0
 OS: Linux
 OS Details: RedHat 7.2 with garnome
-Status: VERIFIED   
+Status: CLOSED   
 Resolution: DUPLICATE
 Severity: normal
 Priority: Normal
 Component: libglademm
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: michael koziarski com               



--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc: 
Date: Thu,  8 Aug 2002 11:00:34 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19

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=90126

Changed by murrayc usa net 

--- shadow/90126	Thu Aug  8 09:16:33 2002
+++ shadow/90126.tmp.32421	Thu Aug  8 11:00:34 2002
@@ -111,6 +111,15 @@
 "layout disturbance" in our test applications is gone.
 
 So, we have to think about the first pack_start member function. Their
 automatic matching has to be prevented in my eyes. Seems to me that
 have to melt somewhat which was just frozen :-(
 
+
+------- Additional Comments From murrayc usa net  2002-08-08 11:00 -------
+1. Like I said, I will delete those old menu examples. Do any other
+examples have that problem. If so, please create a separate bug, with
+a patch if possible.
+
+2. I don't undertand. Please show the a line of code that has the
+problem, and show me what method overload it tries to use. If it can
+be fixed without making the API more difficult then will.



--__--__--

Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu,  8 Aug 2002 12:02:06 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19

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=90126

Changed by szombath bifab de 

--- shadow/90126	Thu Aug  8 11:00:34 2002
+++ shadow/90126.tmp.7633	Thu Aug  8 12:02:06 2002
@@ -120,6 +120,32 @@
 examples have that problem. If so, please create a separate bug, with
 a patch if possible.
 
 2. I don't undertand. Please show the a line of code that has the
 problem, and show me what method overload it tries to use. If it can
 be fixed without making the API more difficult then will.
+
+------- Additional Comments From szombath bifab de  2002-08-08 12:02 -------
+Calling Box::pack_start(...) mistakenly with Gtk::SHRINK for the
+options parameter like
+
+  pBox->pack_start(widget, Gtk::SHRINK, 2);
+
+actually call the member function void Box::pack_start(Widget& child,
+bool expand, bool fill = true, guint padding = 0), means that we are
+calling 
+
+  pBox->pack_start(widget, true, true, 0);
+
+This is not what the user expects. The possibility to evaluate to the
+wrong function call is evil here. A compile error should happen
+instead, otherwise the enum types are needless.
+
+Just replace in line 66 of examples/menu/menu.cc
+
+   vbox->pack_start(*menu_bar, Gtk::SHRINK, 2);
+
+by
+
+   vbox->pack_start(*menu_bar, Gtk::PACK_SHRINK, 2);
+
+and see the difference in he layout yourself.



--__--__--

Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc: 
Date: Thu,  8 Aug 2002 12:27:04 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19

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=90126

Changed by murrayc usa net 

--- shadow/90126	Thu Aug  8 12:02:06 2002
+++ shadow/90126.tmp.10755	Thu Aug  8 12:27:04 2002
@@ -146,6 +146,13 @@
 
 by
 
    vbox->pack_start(*menu_bar, Gtk::PACK_SHRINK, 2);
 
 and see the difference in he layout yourself.
+
+------- Additional Comments From murrayc usa net  2002-08-08 12:27 -------
+I have no idea why Gtk::SHIRNK is being converted implicitly to bool.
+If we remove the default values then we actually break the API for
+people porting from gtkmm 1.2.
+
+Do any examples need to be fixed?



--__--__--

Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, MHL Schulze t-online de
Cc: 
Date: Thu,  8 Aug 2002 12:30:15 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 89951] Changed - gtkmm cvs doesn't compile with gcc 2.95.3 due to internal compiler error

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=89951

Changed by murrayc usa net 

--- shadow/89951	Wed Aug  7 07:20:02 2002
+++ shadow/89951.tmp.11240	Thu Aug  8 12:30:15 2002
@@ -135,6 +135,12 @@
 martin ipc-notebook:~/projects/test > g++ test.cc
 test.cc: In method `void foo::thebug()':
 test.cc:28: Internal compiler error.
 test.cc:28: Please submit a full bug report.
 test.cc:28: See <URL:http://www.gnu.org/software/gcc/bugs.html> for
 instructions.
+
+------- Additional Comments From murrayc usa net  2002-08-08 12:30 -------
+Have you submitted that as a gcc bug report?
+
+Maybe you, or someone, could write a configure-time test that detects
+this and sets a #define.



--__--__--

Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu,  8 Aug 2002 13:17:57 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19

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=90126

Changed by szombath bifab de 

--- shadow/90126	Thu Aug  8 12:27:04 2002
+++ shadow/90126.tmp.16893	Thu Aug  8 13:17:57 2002
@@ -153,6 +153,23 @@
 ------- Additional Comments From murrayc usa net  2002-08-08 12:27 -------
 I have no idea why Gtk::SHIRNK is being converted implicitly to bool.
 If we remove the default values then we actually break the API for
 people porting from gtkmm 1.2.
 
 Do any examples need to be fixed?
+
+------- Additional Comments From szombath bifab de  2002-08-08 13:17 -------
+That what I still see in the examples
+
+examples/menu/menu.cc:    vbox->pack_start(*menu_bar, Gtk::SHRINK, 2);
+examples/menu/menu3.cc:   vbox->pack_start (*menubar, Gtk::SHRINK);
+examples/packbox/packbox.cc:    m_box1.pack_start(m_seperator2,
+Gtk::SHRINK, 5);
+examples/progressbar/progressbar2.cc:    vbox.pack_start(align,
+Gtk::SHRINK, 5);
+examples/progressbar/progressbar2.cc:    vbox.pack_start(hseparator1,
+Gtk::SHRINK);
+examples/progressbar/progressbar2.cc:    vbox.pack_start(hseparator2,
+Gtk::SHRINK);
+examples/progressbar/progressbar2.cc:    vbox.pack_start(button,
+Gtk::SHRINK);
+Hopefully, we dont have such pitfalls in the library code.



--__--__--

Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu,  8 Aug 2002 14:31:45 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 90126] Changed - Layout disturbances with gtkmm-1.3.19

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=90126

Changed by szombath bifab de 

--- shadow/90126	Thu Aug  8 13:17:57 2002
+++ shadow/90126.tmp.25507	Thu Aug  8 14:31:45 2002
@@ -170,6 +170,55 @@
 Gtk::SHRINK);
 examples/progressbar/progressbar2.cc:    vbox.pack_start(hseparator2,
 Gtk::SHRINK);
 examples/progressbar/progressbar2.cc:    vbox.pack_start(button,
 Gtk::SHRINK);
 Hopefully, we dont have such pitfalls in the library code.
+
+------- Additional Comments From szombath bifab de  2002-08-08 14:31 -------
+> I have no idea why Gtk::SHIRNK is being converted 
+> implicitly to bool.
+
+Well, that's the way it goes: Enums are as integral types convertible,
+thus they get implicitly converted to int (but not the opposite way),
+and int are implicitly converted to bool.
+
+A small example for the doubters:
+
+$ cat test.cc
+#include <iostream>
+using namespace std;
+
+enum Case { One=1, Two=2 };
+
+int main()
+{
+  int a = One;
+  bool b = Two;
+
+  cout << "a = " << a << endl
+       << "b = " << (b ? "true" : "false") << " (" << b << ")" << endl;
+  return 0;
+}
+
+$ g++ test.cc
+$ ./a.out 
+a = 1
+b = true (1)
+
+$ CC test.cc # Sun Forte C++
+$ ./a.out 
+a = 1
+b = true (1)
+
+
+I dont see any way to improve the situation with respect to the enums
+here. Normally in class scope we could overload the conversion
+operators to dump a warning at least, but enums have no scope.
+
+When the overloaded pack_start member function exists only for
+compatibility reasons, then we could pricipally surround their
+definition by a define which could switch the visibility of all old
+backward compatibility functions to the compiler. By setting this
+define the user would have a chance to let the compiler check the type
+safety of the function call.
+




--__--__--

_______________________________________________
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]