Gtkmm-forge digest, Vol 1 #1048 - 2 msgs

[gtkmm-forge-request lists sourceforge net]

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 135978] We use GdkEvent* instead of Gdk::Event in the API. (gtkmm (bugzilla.gnome.org))
   2. [Bug 135978] We use GdkEvent* instead of Gdk::Event in the API. (gtkmm (bugzilla.gnome.org))

--__--__--

Message: 1
To: gtkmm-forge lists sourceforge net
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 29 Jan 2006 00:29:55 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 135978] We use GdkEvent* instead of Gdk::Event in the API.

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=3D135978
 gtkmm | general | Ver: 2.4


jonner changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
                 CC|                            |jonathon jongsma gmail c=
om




------- Comment #1 from jonner  2006-01-29 05:29 UTC -------
Is API compatibility the issue here?  I really like the idea of not expos=
ing
the GdkEvent structure directly within gtkmm (if for no other reason than=
 that
you have to actually go read the GTK documentation to figure out what a
GdkEvent is -- it's not in the gtkmm documentation).


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


--__--__--

Message: 2
To: gtkmm-forge lists sourceforge net
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 29 Jan 2006 02:58:52 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 135978] We use GdkEvent* instead of Gdk::Event in the API.

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=3D135978
 gtkmm | general | Ver: 2.4





------- Comment #2 from Murray Cumming  2006-01-29 07:58 UTC -------
> Is API compatibility the issue here?

Probably for at least some of the API - for instance, we can't add (virtu=
al)
default signal handlers without breaking ABI, and we certainly can't chan=
ge the
existing ones. Maybe there are some uses of GdkEvent in methods that we c=
an
just deprecate-and-replace.

But one day we will have an opportunity to break API and I'd like to have=
 this
ready for that time. The GdkEvent structs are a hierarchy but they don't =
use
the regular GObject class system - that's probably why we didn't wrap the=
m so
far. It might not be complicated though.


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
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