Horst Herb wrote:
On Thursday 05 October 2006 17:39, Richard Hosking wrote:
The problem of communication between objects never seemed to be
satisfactorily solved in C++ - Qt used the signals/slots mechanism,
wxWidgets appears to use validators. The details of how these worked
appeared to me to be quite arcane and impenetrable.
"Validators" have nothing to do with messaging in wxWidgets, they are just
callback methods that are called automatically whenever widget content is
modified
You are right - the messaging in wxWigets consisted of the ID for widget
events, the DECLARE_EVENT_TABLE macro, the event table itself and the
handlers. I dont know what the various macros do - they are buried
somewhere.
Still I always seemed to run into scope problems in getting objects to a
called widget and back again. Even with global variables/objects (which
I presume are generally frowned upon)
The validators appear to be a way to get an object to a widget and
returned again when it is modified, with type validation on the way. It
is awful hard to follow though.
How does Ruby do messaging?
R
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
