I am a software engineer. I have been working with C++, MFC, and net technologies for 15 years. I like video games and reading books.
1. Event Coding
An event is a kind of ‘Something Happened’. Some examples are the button got pressed; a checkmark from the check box is removed. We call these kinds of actions Events.
So let us consider a form that has a button in it. We all know that a button can be clicked. The user does the action of clicking a button and we as code writers do not know when that action will happen. Now, let us say, we would like to write a code which says, “Hello There” whenever a user clicks the button.
We will say, “Not a big deal. Double click the button, the Development Environment will bring us to a function, and write the code there which says “Hello There” to the user.
Well. the Team Lead (Yes, the same guy who always bugs us) asks you, “Hey! We have a Class called ProductStock, and it maintains the stock in hand in an integer variable. Can you expose an event say Low-Stock so that the clients of our Class can provide a handler function to handle the situation their own way?”. This will end up thinking about exposing our own event in the ProductStock Class and the event is called “Custom Event”.
2. Publish and Subscribe
If we go back to the button click on the form that says “Hi there”, there are some pieces of information we need to know.
- A Container can hold one or more Components. The button is placed on the form which is a Component. The form is a Container which holds the button.
- The Button class in dot net exposes an event called Click. So button class is the Publisher of the event click.
- The Form class wants to know when the button got clicked. So it subscribes to the published Click Event. We call the Form a Subscriber of the Event.
- When the Button on the Form is clicked, it notifies the Subscriber of the Click Event. And there is an Event Handler code that says “Hi There”, when the notification is received.
So the publish is nothing but exposing the event and subscribe is a kind of getting the notification on the event handler function. Delegates and Events are tightly coupled. We will see how when we are writing our code example.
3. About The Example
In this example, we have two classes. One is the ProductStock class, which maintains the current stock of the product. The other class is Counter which is used by the Billing Counter computers in the retail shop. Let us say; the customer comes to any Billing Counter, informs the product he wants to purchase, pays the bill and goes to the storeroom to receive the product. Each Billing Counter receives a notification when the product stock goes low.
Consider the below picture before we move on:
The above picture explains the following:
- The ProductStock class publishes the event, LowStock.
- Purchase, Counter, etc Classes subscribes to the Published event, LowStock.
- ProductStock sends the notification to the entire subscribers when the ProductStock goes low.
In our example, we are not going to Implement Purchase Class and a Class named Someother.
4. The ProductStock Class: Event Publisher
1) The ProductStock has two member variables. One is to know the product name, and another one is to keep track of the current stock. The current stock gets reduced by the sales counter when a sale of the product is performed.
Read More From Owlcation
2) This Class declares a Multicast Delegate called OnStockLow that takes an Event Source object and EventArgs object. The Event Source here is ProductStock as it will raise the Notification Event. EventArgs Class can pack the information related to the Event. To keep this example simple, we have derived no object from EventArgs. We declare the Multicast Delegate as shown below:
3) Next, we declare the StockLow Event. Note, how the Delegate is coupled with the Event. It implies that the notification handler function should return void. In Addition, it must receive the object as a first parameter and EventArgs as the second parameter. As it is a Multicast Delegate, one can use Delegate Chain of the above-said functions. OK, Now the Product stock published the Event. Below is the declaration of the Event:
Note the syntax:
public event <delegate type name> <event_name>.
4) The constructor of the ProductStock class initializes the members ProductName and StockInHand. Below is the code:
5) All the Counter objects call the ReduceStock function when a sale is performed. This function reduces the current stock. It also notifies the subscriber of the LowStock event when the current stock goes less than five. Below is the function implementation:
Note that in the above code, call to StockLow(this,arg) is known as Raising an Event or sending a Notification. We are done with the implementation ProductStock class.
5. The Counter Class: Event Subscriber
1) The counter class declares the member variable for the counter name and the constructor initializes the Name. The Sales function takes the ProductStock and the number of products sold. It makes a call to the ReduceStock function after the counter makes a sale. Below is the Implementation code:
2) The counter class implements the notification handler for StockLow. We should note the arguments and the void return type. Because this is the rule which is expected by the delegate OnLowStock coupled with the event StockLow. Below is the handler:
6. The Main Program: Client Code
Now, we will see how the client code works. Before that a small refresh on what we did. The ProductStock class exposes an event StockLow, and that event is coupled to OnStockLow Delegate. ReduceStock function raises the StockLow event when the product stock goes below five. The counter class implements the notification handler (LowStockHandler) to receive the notification. Where is the piece of code that links the LowStockHandler to the StockLow event? We link that in the client code which we will write in this section.
1) First, the client creates the two billing counter objects. Below is the code for billing counter:
2) Next, we create three ProductStock objects. These products will be sold through two counters which we created in the previous step. Below is the code:
3) Next, we subscribe to the Event LowStock published by the ProductStock class. We do this by creating a Delegate which points to the Notification handler function. Note, we already implemented the handler in the Counter Class and here we are just binding it to Event. Below is the code:
4) We set up Everything and we sell the products to see the notification when the stock goes below 5. We can also put a breakpoint on the below piece of code and examine how the Events work. Below is the code:
The complete Code Example and its output is given below:
Custom Events Example: Code & Output
© 2018 sirama