GNOME.org
 

Gtkmm-forge digest, Vol 1 #828 - 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. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 160756] patch which add --disable-demos to configure script (bugzilla-daemon bugzilla gnome org)
   2. [Bug 137591] Build failure when building in a Cygwin/win32 environment (bugzilla-daemon bugzilla gnome org)
   3. [Bug 160734] Gtk::MessageDialog doesn't manage buttons correctly (bugzilla-daemon bugzilla gnome org)
   4. [Bug 137591] Build failure when building in a Cygwin/win32 environment (bugzilla-daemon bugzilla gnome org)
   5. [Bug 160244] Long filenames are not correctly distributed. (bugzilla-daemon bugzilla gnome org)
   6. [Bug 138259] Monitoring I/O examples need to be updated (bugzilla-daemon bugzilla gnome org)
   7. [Bug 138259] Monitoring I/O examples need to be updated (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 14:33:41 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 160756] patch which add --disable-demos to configure script

http://bugzilla.gnome.org/show_bug.cgi?id=160756
gtkmm | build | Ver: unspecified





------- Additional Comments From murrayc murrayc com  2004-12-16 14:33 -------
Thanks, but I think that it's a very good idea to always have some sanity-checks
in the build, and I don't think the demos take so long compared to the examples.
I also don't consider this very important because people shouldn't build from
source unless they are packagers or testers.

If you are a packager of a sensible distro then I might change my mind.

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


--__--__--

Message: 2
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 14:33:48 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 137591] Build failure when building in a Cygwin/win32 environment

http://bugzilla.gnome.org/show_bug.cgi?id=137591
gtkmm | build | Ver: 2.4





------- Additional Comments From murrayc murrayc com  2004-12-16 14:33 -------
Any progress, Roger?

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


--__--__--

Message: 3
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 14:54:40 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 160734] Gtk::MessageDialog doesn't manage buttons correctly

http://bugzilla.gnome.org/show_bug.cgi?id=160734
gtkmm | general | Ver: 2.4

murrayc murrayc com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From murrayc murrayc com  2004-12-16 14:54 -------
It looks like it's not an ORable field. It's just a simple enum, so you should
use  Gtk::BUTTONS_OK_CANCEL and/or add_button() to get what you want. I am very
surprised that this example has been wrong for so long. Thanks.

I've fixed the book text too.

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


--__--__--

Message: 4
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 15:51:33 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 137591] Build failure when building in a Cygwin/win32 environment

http://bugzilla.gnome.org/show_bug.cgi?id=137591
gtkmm | build | Ver: 2.4





------- Additional Comments From roger whinlatter uklinux net  2004-12-16 15:51 -------
Not yet.  Unfortunately, the project at work I was using Cygwin and Gtkmm for
stalled some months ago, and so I haven't had any need for GTK+ or Gtkmm on
Cygwin myself.  While I will certainly try to look at it, my Debian and Linux
commitments are currently taking a higher priority.

I have a week off work over Christmas, so I'll try to take a look then.  I'll
build against the official Cygwin GTK+ packages, so I'll have to build Gtkmm
2.4.x rather than 2.5/2.6.  Is that OK?


Regards,
Roger

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


--__--__--

Message: 5
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 17:38:20 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 160244] Long filenames are not correctly distributed.

http://bugzilla.gnome.org/show_bug.cgi?id=160244
gtkmm | build | Ver: 2.5

murrayc murrayc com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From murrayc murrayc com  2004-12-16 17:38 -------
Applied to gtkmm-2-4 branch.

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


--__--__--

Message: 6
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 18:41:13 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 138259] Monitoring I/O examples need to be updated

http://bugzilla.gnome.org/show_bug.cgi?id=138259
gtkmm | reference documentation | Ver: 2.5





------- Additional Comments From chris cvine freeserve co uk  2004-12-16 18:41 -------
Created an attachment (id=34920)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=34920&action=view)
An implementation of a streambuffer using Glib::IOChannel


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


--__--__--

Message: 7
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 16 Dec 2004 18:41:51 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 138259] Monitoring I/O examples need to be updated

http://bugzilla.gnome.org/show_bug.cgi?id=138259
gtkmm | reference documentation | Ver: 2.5





------- Additional Comments From chris cvine freeserve co uk  2004-12-16 18:41 -------
Murray,

I have now prepared a standards conforming stream buffer implemented using
Glib::IOChannel.  This is attached with two example programs.  One demonstrates
what it can do, and the other is a reimplementation of the example program in
gtkmm I sent you which reads and writes to a fifo.

All the buffering is done by Glib::IOChannel, which makes the implementation
quite simple.  There is a two character read buffer, but that is in order to
comply with the standard in having at least one character available for putback
and one character available for peeking.  The slight disadvantage is that
std::istream::readsome() (and similarly is_avail()) will not be of much use, as
there will only be a character available for them if there has been a peek or a
putback.  However, the standard does not require readsome() to provide anything
- it only requires it to return without blocking, and if it can fetch something
from the buffer on the way without any system reads then to provide it.

If you are interested in making more of it (say putting it in Glib) let me know
and I will put it in a form suitable for that purpose, including giving it a new
name.  There is probably some refinements I could come up with if I thought
about it.  It is a considerable improvement on Glib::StreamIOChannel.

Chris

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact 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]