Wow, having been dubbed the king of bad analogies, and justifiably so, it really feels 
weird to get complimented for one. Especially
because it took male pattern baldness and color loss to bring out the best in me. 
hehehe (Thanks BTW)

Even so, I'll have to disagree with you on this one. In order to hook up to the 
individual hair you have to first find it. That
would take a proactive scan through potentially all the hairs, not just the minor 
percentage of those that have fallen out. Not to
mention the closely coupled monitoring, and the extra weight of the invocation list 
may make the curly little guy uncomfortable
enough to jump before his time.

I'd extend the comb and let it straighten this out too... <gd&r>

While you are busy looking for that proverbial needle in a hair stack so you can hook 
up a callback to it, I'll be basking on the
beach, comfortable in my knowledge that I'll be notified "if and when". Less cycles 
all around. ;-)

public class OriginalHairWatcherComb : Comb
  public event HairLoss LastOriginalHairGone;

  public override void OnHairLoss(object sender, HairLossEventArgs e) {
    if ((Color.Gray != e.Color) && (null != LastOriginalHairGone))
      LastOrigalHairGone(this, e);

    //Ignore gray hair loss...
    //base.OnHairLoss(sender, e);
  }
}


Keep Smilin'
Ed Stegman

-----Original Message-----
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]]On Behalf Of Graeme Foster
Sent: Wednesday, September 11, 2002 5:49 AM
To: [EMAIL PROTECTED]
Subject: Re: event granularity


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.

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to