[gtkmm] RE: tutorial appendix B on signals misleading



Thanks, but please see www.gtkmm.org/bugs.shtml about creating patches.

Murray Cumming
www.murrayc.com
murrayc usa net

> -----Original Message-----
> From: Nathan Hurst [mailto:njh hawthorn csse monash edu au] 
> Sent: Donnerstag, 15. Januar 2004 13:10
> To: Murray Cumming Comneon com
> Cc: Nathan Hurst infotech monash edu au; gtkmm-list gnome org
> Subject: Re: tutorial appendix B on signals misleading
> 
> 
> Murray Cumming Comneon com wrote:
> 
> >Yes. Thanks for noticing that. Feel free to submit a patch. 
> It should 
> >explain it and also explain that Gtk widgets do this automatically.
> >
> >Murray Cumming
> >www.murrayc.com
> >murrayc usa net
> >  
> >
> 
> --- docs/tutorial/gtkmm-tut-with-examples.xml   2004-01-15 
> 22:22:35.000000000 +1100
> +++ docs/tutorial/gtkmm-tut-with-examples-njh.xml       2004-01-15 
> 23:08:25.000000000 +1100
> @@ -11005,7 +11005,7 @@
>  <programlisting>
>  void on_button_clicked();
>  
> -class some_class
> +class some_class : public SigC::Object
>  {
>      void on_button_clicked();
>  };
> @@ -11029,7 +11029,7 @@
>  second argument is a pointer to one of its methods.  This 
> particular  version of <literal>slot()</literal> creates a 
> slot which will, when 
> "called", call
>  the pointed-to method of the specified object, in this case 
> -some_object.on_button_clicked().
> +some_object.on_button_clicked().  Note that some_class must 
> be derived
> from <literal>SigC::Object</literal> - most classes will be 
> derived from 
> a Gtk::Widget which includes <literal>SigC::Object</literal> 
> as an ancestor.  </para>
>  
>  <para>
> 
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]