¿Cómo activo un evento declarado en otra clase?

How do I trigger an event declared in another class?

The field will either be null, if no client has hooked up a delegate to the event, or else it refers to a delegate that should be called when the event is invoked. Thus, invoking an event is generally done by first checking for null and then calling the event. Invoking an event can only be done from within the class that declared the event.

You can write a public method on the class you want the event to fire from and fire the event when it is called. You can then call this method from whatever user of your class. Of course, this ruins encapsulation and is bad design.

Define a field in your external class with type of your event delegate. get the the reference of that field in the constructor of external class and save it. In main class of your event, send the reference of event for delegate of external class.

The raised event will in turn call the handler of the event in the EventContainer class. Something like this (this is obviously not correct): This old post raises an issue that can easily be circumvented using an event hub like TinyMessenger. – Larry Apr 7 ’17 at 9:49 This is not possible, Events can only be risen from inside the class.

To enable a class to trigger work flow, it has to implement interface IF_WORKFLOW. When it is implemented it also implements INTERFACE : BI_OBJECT and BI_PERSISTENT. Step5. In the attribute section define two attribute and one choose as key attribute. Step6. In the Events section, define an event. Now goto methods section. Step7.

In Developer, log in to a project source. You must log in as a user with the Create And Edit Schedules And Events privilege. Go to Administration > Configuration Managers > Events. The list of events for the project source displays on the right-hand side. Select File > New > Event. Name the new event.

If your class raises multiple events, the compiler generates one field per event delegate instance. If the number of events is large, the storage cost of one field per delegate may not be acceptable. For those situations, .NET provides event properties that you can use with another data structure of your choice to store event delegates.