Propagating events

[Bevo]

What is the correct technique when firing events that must be propagated up
the call stack?

I have a class A that instantiates a class B that instantiates class C. C is
firing an event that A needs to response to. I have implemented it this way:

C fires event CEvent. B (subscriber of CEvent) picks it up and fires its own
event BEvent by just passing through the event args from CEvent. A
(subscriber of BEvent) picks up BEvent and takes proper action.

Is this the correct technique ot is it another and more convenient way to do
it?

[Sameeksha MCAD.Net]

Class B can just catch the event and throw it in the catch block so that it
is propogated to B's parent, that is class A.

"Bevo" wrote:

What is the correct technique when firing events that must be propagated up
the call stack?

I have a class A that instantiates a class B that instantiates class C. C is
firing an event that A needs to response to. I have implemented it this way:

C fires event CEvent. B (subscriber of CEvent) picks it up and fires its own
event BEvent by just passing through the event args from CEvent. A
(subscriber of BEvent) picks up BEvent and takes proper action.

Is this the correct technique ot is it another and more convenient way to do
it?

[billr]

Sameeksha : the op's question was Events NOT Exceptions.
========

Bevo : your approach is perfectly acceptable
====

--
Of all words of tongue and pen, the saddest are: "It might have been"

Bill.Richards @ greyskin .co .uk
http://greyskin.co.uk
"Sameeksha MCAD.Net" wrote:

Class B can just catch the event and throw it in the catch block so that it
is propogated to B's parent, that is class A.

"Bevo" wrote:

What is the correct technique when firing events that must be propagated up
the call stack?

I have a class A that instantiates a class B that instantiates class C. C is
firing an event that A needs to response to. I have implemented it this way:

C fires event CEvent. B (subscriber of CEvent) picks it up and fires its own
event BEvent by just passing through the event args from CEvent. A
(subscriber of BEvent) picks up BEvent and takes proper action.

Is this the correct technique ot is it another and more convenient way to do
it?

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

This method is good, B has two options, either expose C as public and allow
it to be directly accesible to the callers or just keep it private and just
derefine C's members he wants to be accesible to clients using B.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Bevo" <Be**@discussions.microsoft.com> wrote in message
news:BF**********************************@microsof t.com...

What is the correct technique when firing events that must be propagated
up
the call stack?

I have a class A that instantiates a class B that instantiates class C. C
is
firing an event that A needs to response to. I have implemented it this
way:

C fires event CEvent. B (subscriber of CEvent) picks it up and fires its
own
event BEvent by just passing through the event args from CEvent. A
(subscriber of BEvent) picks up BEvent and takes proper action.

Is this the correct technique ot is it another and more convenient way to
do
it?