Why inherit from eventargs

I'm not referencing some actual instance of a ScriptableObject. I want to be able to use the functionality it provides, whilst still being able to polymorph my proposed class in to an EventArgs type. No need to be sorry, thanks a lot for expanding.

I'm going to have to take an hour or so to wrap my head around all of this I've only been using Unity and C for a week or so. Attachments: Up to 2 attachments including images can be used with a maximum of To help users navigate the site we have posted a site navigation guide. Make sure to check out our Knowledge Base for commonly asked Unity questions.

Answers Answers and Comments. Interaction script 2 Answers. When to use 'delegate', 'event' or 'Action'? Destroy gameObject only works once 1 Answer. Viewed 5k times. I don't understand why inheriting from EventArgs is useful. I also want to learn how I can call this code block from default. Improve this question. I can't find an example necessarily for this for a ASP. NET scenario.

In web application this type of event is usually handled client side through JavaScript. I guess it is possible to create a custom control that will pass along these info from JavaScript in a PostBack. Add a comment. Active Oldest Votes. Improve this answer. Jon Skeet Jon Skeet 1. There is one very mild advantage to EventArgs over simply using object. The delegate having the signature object, object is more prone to a being called errorenously due to typos in the code.

With a signature of object, EventArgs such a typo is much more likely to be spotted at compile time. NET 4 source. Represents the base class for classes that contain event data, and provides a value to use for events that do not include event data. The following example shows a custom event data class named ThresholdReachedEventArgs that derives from the EventArgs class. An instance of the event data class is passed to the event handler for the ThresholdReached event.

This class serves as the base class for all classes that represent event data. For example, the System. AssemblyLoadEventArgs class derives from EventArgs and is used to hold the data for assembly load events.

To create a custom event data class, create a class that derives from the EventArgs class and provide the properties to store the necessary data. The name of your custom event data class should end with EventArgs. To pass an object that does not contain any data, use the Empty field.

For more information about events, see the Handling and Raising Events article.