Processing Events
Event processing deals with the conversion of standardized event codes to product-specific event codes and GUI events to ABAP events.
Integration
If there is interaction in a graphic it creates and raises an event. This event has to be processed in the back end.
First, an event has to be registered. This is to minimize communication between the back end and the front end. The application registers the standardized (internal) event code with the graphics proxy. The graphics proxy registers the event code (converted to a product-specific code) with the Control Framework. For more information, see the documentation on the Control Framework.
If the graphic creates and raises this event the graphics proxy writes data changes to the data container (if necessary) and converts the product-specific event code to a standardized ABAP event. This ABAP event can then be handled by the application.
Note
It is event codes that are sent from the application to the graphics proxy and from the graphics proxy to the Control Framework. It is events that are sent back in the other direction.
Features
Some ABAP events are sent by all graphics proxies (for example, GRAPHIC_ANYEVT). These events are defined and documented in the graphics proxy interface (IF_GRAPHIC_PROXY). Graphics proxies can also have their own event interface in their class definition.
Activities
Every graphics proxy distributes its internal event with a special ABAP event (for example, GRAPHIC_SELECTED) and also the ABAP event GRAPHIC_ANYEVT.