Whole document tree
bonobo-listenerSynopsis
DescriptionThe BonoboListener object is a CORBA server used to receive events emitted by a remote Bonobo::EventSource server. The combination EventSource/Listener is used to notify one or more client applications of events that happen in a component. Think of the EventSource/Listener as a notification/callback system that allows multiple clients to be informed of events. Once created, the BonoboListener object needs to be attached to a remote IDL:Bonobo/EventSource:1.0 server. This is done by passing the CORBA Object reference of the BonoboListener to the addListener method in the IDL:Bonobo/EventSource:1.0. The BonoboListener object allows the user to specify a callback function to be invoked when an event is emitted by the IDL:Bonobo/EventSource:1.0 server. The BonoboListener object also emits the "event_notify" Gtk+ signal, which allows you to connect multiple code segments to the same event notification. Here is a sample client application that registers interest in being notified of events from the fictional "Keyboard" event source:
The CORBA::any value passed to the listener function is defined by the contract between the EventSource's event you are using and you. To manipulate the value, you can use the CORBA DynamicAny interface to introspect the value and extract the information you need. DetailsBONOBO_LISTENER()
BONOBO_LISTENER_CLASS()
BONOBO_IS_LISTENER_CLASS()
BonoboListenerClass
BonoboListenerCallbackFn ()
The signature for the callback function invoked when an event is delivered to the BonoboListener object. bonobo_listener_new ()
Creates a generic event listener. The listener calls the event_callback function and emits an "event_notify" signal when notified of an event. The signal callback should be of the form: <informalexample> <programlisting> void some_callback (BonoboListener *listener, char *event_name, CORBA_any *any, CORBA_Environment *ev, gpointer user_data); </programlisting> </informalexample> You will typically pass the CORBA_Object reference in the return value to an EventSource (by invoking EventSource::addListener). bonobo_event_make_name ()
Creates an event name. Event names consist of three parts. The idl_path is mainly to create a unique namespace, and should identify the interface which triggered the event, for example "Bonobo/Property". The kind denotes what happened, for example "change". Finally you can use the optional subtype to make events more specific. All three parts of the name are joined together separated by colons. "Bonobo/Property:change" or "Bonobo/Property:change:autosave" are examples of valid event names. |