After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 138254 - sigc -- slot, bind, etc. fixes to documentation
sigc -- slot, bind, etc. fixes to documentation
Status: RESOLVED FIXED
Product: gtkmm
Classification: Bindings
Component: reference documentation
2.4
Other Linux
: High normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2004-03-26 23:35 UTC by Elijah Newren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
My guesses at fixing some of the sigc problems in the documentation (1.93 KB, patch)
2004-03-26 23:36 UTC, Elijah Newren 		none Details | Review

Description Elijah Newren 2004-03-26 23:35:32 UTC 
I'll attach a patch which I think solves some of the problems I found in the
tutorial (I'm a little unsure of some of them, though).  There's others that I
didn't understand well enough to guess the correct fix (or even to understand
for sure whether it was right or wrong):

1) tutorial/html/ch17s03.html uses Slot0<int>.  Should this be sigc::slot<int>
or something similar?

2) tutorial/html/ch17s02.html refers to a SlotType.  From grepping through the
source code, it appears that a SlotType is a typedef.  Could this be mentioned
in the tutorial?  I couldn't find the appropriate connection function (perhaps I
was grepping in the wrong place?), so I wasn't able to find the exact typedef,
though I did find some connect functions that looked similar...
Comment 1 Elijah Newren 2004-03-26 23:36:46 UTC 
Created attachment 25992 [details] [review]
My guesses at fixing some of the sigc problems in the documentation
Comment 2 Murray Cumming 2004-03-27 20:32:28 UTC 
OK, these are all fixed in cvs now. Thanks.

> I couldn't find the appropriate connection function (perhaps I
> was grepping in the wrong place?), so I wasn't able to find the exact typedef,
> though I did find some connect functions that looked similar...

This should be no problem with the reference documentation.