William Squires wrote:

>   Oops, I should have given you the 'why' of it.
>   The reason you can't simply put a Timer directly into your class  
>is that - unlike in a window - it doesn't know who to send its Action 
>() event to. By making a Timer subclass (which has a reference to its  
>parent, or owner, class), that subclass can now do something about  
>the Action() event the superclass throws; that is, your subclass has  
>the 'smarts' to handle the Action() event that occurs when the timer  
>fires, and lets its parent object know about it via the callback.
>   HTH!
>  
>

Ahh. ok.

Well, that answers my questions.

Thanks.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to