Lines Matching full:signal
88 will return false. KApplication will catch a dcop signal and display an
186 will send your signal to all applications called 'konsole'.
281 though. A DCOP signal can be connected to a DCOP function. Whenever the DCOP
282 signal gets emitted, the DCOP functions to which the signal is connected are
286 A DCOP signal originates from a DCOP Object/DCOP Client combination (sender).
291 connections of DCOP signals. In DCOP, unlike Qt, a signal connections can
292 have an anonymous sender and, unlike Qt, a DCOP signal connection can be
295 With DCOP one can connect a signal without specifying the sending DCOP Object
300 Another DCOP feature are so called non-volatile connections. With Qt signal
302 the signal gets deleted. A volatile DCOP signal connection will behave the
303 same. However, a non-volatile DCOP signal connection will not get deleted
307 in that case the signal connection will always be deleted.
312 The following example shows how KLauncher emits a signal whenever it notices
320 The task manager of the KDE panel connects to this signal. It uses an
321 anonymous connection (it doesn't require that the signal is being emitted
326 It connects the clientDied(pid_t) signal to its own clientDied(pid_t) DCOP
327 function. In this case the signal and the function to call have the same name.
328 This isn't needed as long as the arguments of both signal and receiving function
330 of the signal. E.g. it is allowed to connect the clientDied(pid_t) signal to
