[gtkmm] Gtkmm-forge digest, Vol 1 #549 - 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 126163] Changed - libgdamm package config dependency problem (bugzilla-daemon widget gnome org)
   2. [Bug 126149] Changed - Toolbar + stlport (bugzilla-daemon widget gnome org)
   3. [Bug 126213] Changed - maybe signals-with-return-types should connect_before (bugzilla-daemon widget gnome org)
   4. [Bug 89780] Changed - Treeview: signal_button_press_event needs connect_notify() (bugzilla-daemon widget gnome org)
   5. [Bug 125969] Changed - Scale button_pressed_event needs connect_notify() (bugzilla-daemon widget gnome org)
   6. [Bug 126213] Changed - maybe signals-with-return-types should connect_before (bugzilla-daemon widget gnome org)
   7. [Bug 126324] New - Problem compiling gtkmm 2.2.8 (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, bland mail ru
Cc: 
Date: Wed,  5 Nov 2003 02:32:17 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 126163] Changed - libgdamm package config dependency problem

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

Changed by murrayc usa net 

--- shadow/126163	Tue Nov  4 20:15:21 2003
+++ shadow/126163.tmp.19382	Wed Nov  5 02:32:17 2003
@@ -32,6 +32,11 @@
 
 
 ------- Additional Comments From bland mail ru  2003-11-04 20:14 -------
 Created an attachment (id=21202)
 Proposed patch
 
+
+------- Additional Comments From murrayc usa net  2003-11-05 02:32 -------
+Now I understand. Thanks. I had never tried to use the libgdamm .pc 
+file because I can't even get the examples to work. I will apply this 
+later.


--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed,  5 Nov 2003 02:55:37 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 126149] Changed - Toolbar + stlport

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

Changed by bux mail15 com 

--- shadow/126149	Tue Nov  4 12:30:40 2003
+++ shadow/126149.tmp.28873	Wed Nov  5 02:55:37 2003
@@ -43,6 +43,64 @@
 it would be nice to have an actual test case for this, but I guess you
 should just be able to name one of the examples for us.
 
 Personally, I have no great incentive to do the work myself.
 
 Also, do all the libsigc++ tests work successfully?
+
+------- Additional Comments From bux mail15 com  2003-11-05 02:55 -------
+I post a full example here:
+
+#include <gtkmm.h>
+
+class ExampleWindow : public Gtk::Window
+{
+private:
+  Gtk::Toolbar toolbar;
+  Gtk::VBox box;
+
+public:
+  ExampleWindow();
+  ~ExampleWindow();
+
+protected:
+  virtual void action();
+};
+
+ExampleWindow::ExampleWindow()
+{
+  set_default_size(640, 480);
+  add(box);
+  box.pack_start(toolbar, Gtk::PACK_SHRINK);
+
+  toolbar.tools().push_back(Gtk::Toolbar_Helpers::ButtonElem("Test",
+SigC::slot(*this, &ExampleWindow::action), "testing"));
+
+  show_all_children();
+}
+
+ExampleWindow::~ExampleWindow()
+{}
+
+void ExampleWindow::action()
+{
+  hide();
+}
+
+int main(int argc, char *argv[])
+{
+  Gtk::Main kit(argc, argv);
+
+  ExampleWindow window;
+  Gtk::Main::run(window);
+
+  return 0;
+}
+
+compile this with this and it will work:
+g++ code.cpp `pkg-config gtkmm-2.0 --cflags --libs`
+
+and not with this (well it will compile and link but it won't run)
+g++ code.cpp `pkg-config gtkmm-2.0 --cflags --libs` -I/usr/include/stlport
+
+I will test the libsigc++ examples later today when I get more time
+for it.


--__--__--

Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, murrayc usa net
Cc: 
Date: Wed,  5 Nov 2003 07:09:48 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 126213] Changed - maybe signals-with-return-types should connect_before

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

Changed by murrayc usa net 

--- shadow/126213	Tue Nov  4 12:38:12 2003
+++ shadow/126213.tmp.22407	Wed Nov  5 07:09:48 2003
@@ -10,12 +10,13 @@
 Component: object
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: murrayc usa net               
 TargetMilestone: ---
 URL: 
 Summary: maybe signals-with-return-types should connect_before
+OtherBugsDependingOnThis: 89780
 
 I think that all signals connect after (so the signal handlers are called
 after existing signal handlers). signals with return types (such as the
 bool *_event signals) also have connect_notify() which connect before, but
 ignore the return value. A normal connect is often impossible because the
 return value has stopped any further processing. Maybe these signals should


--__--__--

Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, steve przepiora org
Cc: 
Date: Wed,  5 Nov 2003 07:09:47 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 89780] Changed - Treeview: signal_button_press_event needs connect_notify()

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

Changed by murrayc usa net 

--- shadow/89780	Fri Sep 26 02:58:06 2003
+++ shadow/89780.tmp.22387	Wed Nov  5 07:09:47 2003
@@ -10,12 +10,13 @@
 Component: TreeView
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: steve przepiora org               
 TargetMilestone: ---
 URL: 
 Summary: Treeview: signal_button_press_event needs connect_notify()
+BugsThisDependsOn: 126213
 
 I have a tree with a pixbufrenderer and a textrenderer, I have attached a
 callback for on button press, and activated(the example doesn't have the
 activated handler).
 
 When clicking on the text widget the signal handler is not called, also


--__--__--

Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, chalil boun edu tr
Cc: 
Date: Wed,  5 Nov 2003 07:10:46 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 125969] Changed - Scale button_pressed_event needs connect_notify()

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

Changed by murrayc usa net 

--- shadow/125969	Tue Nov  4 08:48:50 2003
+++ shadow/125969.tmp.23418	Wed Nov  5 07:10:46 2003
@@ -9,13 +9,14 @@
 Priority: Normal
 Component: general
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: chalil boun edu tr               
 TargetMilestone: ---
 URL: 
-Summary: scales and scroolbars doesn't emit pressed/released signals
+Summary: Scale button_pressed_event needs connect_notify()
+BugsThisDependsOn: 126213
 
 i see this bug when i want know Gtk::VScale pressed and released in my 
 application.Pressed signal is emitted when i double click on it but 
 released signal never emitted.Also i try it with glade-2 by creating simple 
 widget.GTK+ is emiting these signals but gtkmm doesn't.Same thing also 
 happened with scroolbars.They also show same behaviour.I am using gtkmm 


--__--__--

Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, murrayc usa net
Cc: 
Date: Wed,  5 Nov 2003 07:10:48 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 126213] Changed - maybe signals-with-return-types should connect_before

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

Changed by murrayc usa net 

--- shadow/126213	Wed Nov  5 07:09:48 2003
+++ shadow/126213.tmp.23462	Wed Nov  5 07:10:47 2003
@@ -10,13 +10,13 @@
 Component: object
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: murrayc usa net               
 TargetMilestone: ---
 URL: 
 Summary: maybe signals-with-return-types should connect_before
-OtherBugsDependingOnThis: 89780
+OtherBugsDependingOnThis: 89780, 125969
 
 I think that all signals connect after (so the signal handlers are called
 after existing signal handlers). signals with return types (such as the
 bool *_event signals) also have connect_notify() which connect before, but
 ignore the return value. A normal connect is often impossible because the
 return value has stopped any further processing. Maybe these signals should


--__--__--

Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed,  5 Nov 2003 18:31:51 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 126324] New - Problem compiling gtkmm 2.2.8

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

Changed by pierre42d 9online fr 

--- shadow/126324	Wed Nov  5 18:31:51 2003
+++ shadow/126324.tmp.1250	Wed Nov  5 18:31:51 2003
@@ -0,0 +1,71 @@
+Bug#: 126324
+Product: gtkmm
+Version: 2.2
+OS: Linux
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: normal
+Priority: Normal
+Component: build
+AssignedTo: gtkmm-forge lists sourceforge net                            
+ReportedBy: pierre42d 9online fr               
+TargetMilestone: ---
+URL: 
+Summary: Problem compiling gtkmm 2.2.8
+
+gmake[5]: Entering directory `/tmp/gtkmm-2.2.8/gdk/gdkmm'
+if /bin/sh ../../libtool --mode=compile g++ -s -DHAVE_CONFIG_H
+-DG_LOG_DOMAIN=\"gdkmm\" -Dgdkmm_COMPILATION -DG_DISABLE_DEPRECATED
+-DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED
+-DGTK_DISABLE_DEPRECATED  -I../../glib -I../../glib -I../../pango
+-I../../pango -I../../atk -I../../atk -I../../gdk -I../../gdk -I../../gtk
+-I../../gtk -I/usr/local/lib/sigc++-1.2/include
+-I/usr/local/include/sigc++-1.2 -I/usr/local/include/gtk-2.0
+-I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0
+-I/usr/local/include -I/usr/X11R6/include -I/usr/local/include/pango-1.0
+-I/usr/local/include/freetype2 -I/usr/local/include/glib-2.0
+-I/usr/local/lib/glib-2.0/include -pthread -I/usr/local/include/glib-2.0
+-I/usr/local/lib/glib-2.0/include  -I/usr/local/BerkeleyDB.4.1/include  -O3
+-march=i686 -Wall -MT pixbuf.lo -MD -MP -MF ".deps/pixbuf.Tpo" \
+  -c -o pixbuf.lo `test -f 'pixbuf.cc' || echo './'`pixbuf.cc; \
+then mv -f ".deps/pixbuf.Tpo" ".deps/pixbuf.Plo"; \
+else rm -f ".deps/pixbuf.Tpo"; exit 1; \
+fi
+ g++ -s -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"gdkmm\" -Dgdkmm_COMPILATION
+-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED
+-DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -I../../glib
+-I../../glib -I../../pango -I../../pango -I../../atk -I../../atk
+-I../../gdk -I../../gdk -I../../gtk -I../../gtk
+-I/usr/local/lib/sigc++-1.2/include -I/usr/local/include/sigc++-1.2
+-I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include
+-I/usr/local/include/atk-1.0 -I/usr/local/include -I/usr/X11R6/include
+-I/usr/local/include/pango-1.0 -I/usr/local/include/freetype2
+-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -pthread
+-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
+-I/usr/local/BerkeleyDB.4.1/include -O3 -march=i686 -Wall -MT pixbuf.lo -MD
+-MP -MF .deps/pixbuf.Tpo -c pixbuf.cc  -fPIC -DPIC -o .libs/pixbuf.o
+pixbuf.cc: In member function `void Gdk::Pixbuf::render_to_drawable(const 
+   Glib::RefPtr<Gdk::Drawable>&, const Glib::RefPtr<Gdk::GC>&, int, int, int, 
+   int, int, int, Gdk::RgbDither, int, int)':
+pixbuf.cc:435: error: `gdk_pixbuf_render_to_drawable' undeclared (first use 
+   this function)
+pixbuf.cc:435: error: (Each undeclared identifier is reported only once for 
+   each function it appears in.)
+pixbuf.cc: In member function `void
+Gdk::Pixbuf::render_to_drawable_alpha(const 
+   Glib::RefPtr<Gdk::Drawable>&, int, int, int, int, int, int, 
+   Gdk::PixbufAlphaMode, int, Gdk::RgbDither, int, int)':
+pixbuf.cc:440: error: `gdk_pixbuf_render_to_drawable_alpha' undeclared (first 
+   use this function)
+gmake[5]: *** [pixbuf.lo] Error 1
+gmake[5]: Leaving directory `/tmp/gtkmm-2.2.8/gdk/gdkmm'
+gmake[4]: *** [all-recursive] Error 1
+gmake[4]: Leaving directory `/tmp/gtkmm-2.2.8/gdk/gdkmm'
+gmake[3]: *** [all-recursive] Error 1
+gmake[3]: Leaving directory `/tmp/gtkmm-2.2.8/gdk'
+gmake[2]: *** [all] Error 2
+gmake[2]: Leaving directory `/tmp/gtkmm-2.2.8/gdk'
+gmake[1]: *** [all-recursive] Error 1
+gmake[1]: Leaving directory `/tmp/gtkmm-2.2.8'
+gmake: *** [all] Error 2



--__--__--

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