Lines Matching full:signal
522 Signal messages are notifications that a given signal
538 Header fields might include the sender bus name, destination bus name, method or signal name,
634 <title>Emitting a Signal - Behind the Scenes</title>
637 A signal in DBus consists of a single message, sent by one process to any number of other processes.
638 That is, a signal is a unidirectional broadcast. The signal may contain arguments (a data payload), but
644 The emitter (aka sender) of a signal has no knowledge of the signal recipients. Recipients register
646 the signal name. The bus daemon sends each signal only to recipients who have expressed interest in that
647 signal.
651 A signal in DBus happens as follows:
655 A signal message is created and sent to the bus daemon. When using the low-level API this may be
657 emits a native signal or event.
662 The signal message contains the name of the interface that specifies the signal;
663 the name of the signal; the bus name of the process sending the signal; and
675 The bus daemon examines the signal and determines which processes are interested in it.
676 It sends the signal message to these processes.
681 Each process receiving the signal decides what to do with it; if using a binding,
682 the binding may choose to emit a native signal on a proxy object. If using the
683 low-level API, the process may just look at the signal sender and name and decide
1091 <sect2 id="glib-signal-connection">
1098 the signature of your signal handlers; you may then invoke
1103 marshaller for the type signature of a remote signal. In that
1888 to register a signal handler on the bus. One way is to attach to an already created proxy using the connect_to_signal method
1889 which takes a signal name and handler as arguments. Let us look at an example of connecting to the HAL service to receive
1922 your signal handler. While HAL is guaranteed to be around on systems that use it this is not always the case for every
1923 service on the bus. Say our program started up before HAL, we could connect to the signal by adding a signal receiver
1947 a reference to the object so once a signal was received operations could be executed on the object.
1950 <title>Signal matching on arguments</title>
1953 bindings you can now add a match on arguments being sent in a signal.
2122 @dbus.service.signal('org.freedesktop.HelloWorldIFace')
2130 object.hello_signal('I sent a hello signal')
2137 Adding a @dbus.service.signal decorator to a method turns it into a signal emitter. You can put code
2139 messages but for the most part a pass noop will do. Whenever you call the emitter a signal will be emitted
2140 with the parameters you passed in as arguments. In the above example we send the message 'I sent a hello signal'
2141 with the signal.
