On Wed, Mar 26, 2003 at 03:22:43PM +0100, Antoon Pardon wrote:
> > Events are things sent to the application by the X server. Signals are
> > a generic notification system used in GTK (and related libraries). GTK
> > uses signals to notify your application when events come in.
> >
> > James.
>
> I'm afraid it isn't more clear now.
>
> >From what you write above I would infer that the programmer
> only works with signals, events just being one way in which
> signals can be generated.
But that's precisely what the truth is :-)
> But in the tutorial are two specification on how a callback
> function should look like and these are different for
> events and signals.
Yes, the callback signatures are different, but they also vary between
non-event signals, so that doesn't rule out James statement. However ->
> Anyway if my first interpretation of your words is correct
> and my misunderstand is somewhere else I recommend you
> change the following sentence in section 2.3:
>
> In addition to the signal mechanism described above, there is a set of
> events that reflect the X event mechanism. Callbacks may also be
> attached to these events. These events are:
>
> I think it would be better to write something like:
>
> One way in which signals are used is for communicating
> X-events to the program.
Just one thing, though: the tutorial wasn't written by James :-) I
suppose John can use it in his [con]version of the tutorial, but
otherwise it would make sense to let Tony et al. know of your
suggestion:
http://www.gtk.org/tutorial/ch-contributing.html
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
