On 31-May-07, at 8:07 AM, Karen wrote:
>
> On May 31, 2007, at 3:21 AM, Frank Condello wrote:
>
>> Though I suppose your workaround might not work out so
>> well if you need the owning class to handle a bunch of different
>> timer events.
>
> Having done the same thing about RB 3.5 the answer to that is
> simple. You can pass an optional parameter to the owned timer
> indicating the action to be taken which is passed back when the timer
> calls the method. Then just use a select case statement in the
> callback method.
That's exactly what I meant by "not work out so well" ;) One delegate
handling multiple events can be harder to maintain than using
multiple subclasses in some situations, but it really comes down to
coding style and personal preference most of the time.
Frank.
<http://developer.chaoticbox.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|