Hi,

Sorry for delay in replying - in fact this is still going to have to be short. Just a couple of quick things:

>
The agent mouse_enter added to the list of pointer_enter_actions takes on the visibility of first_label.
>
I understood you to be saying that agent was NOT dependent on the visibility of the object ?

>>
Multiple RaiseEvents(), which is called multicasting, doesn't enjoy the benefit of 'collection', 'iteration', and 'intercommunication'. Neither does the flip side--BindEvent().
>>
Multiple RaiseEvents()? You mean raising the same event from different places? Don't understand the relevance. Multiple BindEvents() - do you mean binding the same method to multiple events or calling multiple methods when an event is raised? If the latter then it is all about collections. Everytime you use it you're adding an additional 'callback function' to the collection that is iterated when the event is raised?

>>
This slightly falls short of what I have in Eiffel, though. In Eiffel, we don't have simply public, protected, or hidden. We have public (export to class ANY), secret (export to class NONE), and selectively public (export to a list of classes that can see the feature, which most of the time are abstract base classes).
>>
The concept of 'selectively public' sounds interesting - but I need time to get my head around it...

Your idea for an 'Event manager' could be implemented without using the VFP BINDEVENT and RAISEEVENT at all but it wouldn't be asynchronous. Come to think of it VFP probably handles events synchronously anyway..

Gotta go, regards,
Viv