At 07:17 PM 4/15/00 -0700, Ben Wing wrote:
I did offer to fax you all the documentation.
I don't have a fax machine.
Don't you have access to the sources? The Athena widgets are open
source.
Somewhere maybe.
I seriously doubt I made this suggestion, since it's so unclean.
At 04:36 AM 4/7/00 -0700, Ben Wing wrote:
(2) [Better] Provide a way for callbacks to determine where they were
invoked
at. This is much more general and is what you should really do. For
example,
have the code that calls the callbacks bind some global variables such
as
widget-callback-current-glyph and widget-callback-current-channel, which
contain the glyph
whose callback is being invoked, and the window or frame of the glyph
(depending on where the glyph is) where the invocation actually happened.
That way, the callbacks can easily figure out the dialog box and
its parent, and not have to worry about embedding it in at creation time.
Obviously transatlantic differences in English meaning are larger than I
thought.
I don't understand when you say "the various types of
callback". Are you
using
the callback for various different purposes?
No. Callbacks are allowed to be many different things - some functions,
others just forms or symbols.
Your widget callbacks should work just like any other callback: they
take two
arguments, one indicating the object to which the callback was attached
(an image
instance, i think), and the event that caused the callback to be
invoked.
I'm obviously misunderstanding something here.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd