Nice analogy. :) What if you had thousands of grey hairs, but only one of your original colour? You might not care about all the grey hairs ending up in your comb, but you would want to know about the coloured one.
In this case, it's neater to just hook up to the individual hair rather than filtering all the uninteresting events from the comb. Cheers, G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Ed Stegman Sent: 11 September 2002 05:12 To: [EMAIL PROTECTED] Subject: Re: event granularity So, if you are interested in watching the rate of hair loss, are you going to hook up a callback to each follicle? Personally, I'd rather just hook up the comb, and let it tell me when a hair gets stuck in there. Any interesting information I need about why the little deserter abandoned post I can get from the hair itself as a member of the HairLossEventArg type. Interestingly, my hair loss is a result of inheritance, which I can also use to extend my hair... What's up with that? ***************************************************************************** The contents of this email and any attachments are confidential. It is intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to any one or make copies. ** eSafe scanned this email for viruses, vandals and malicious content ** ***************************************************************************** You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
