From kde-core-devel Mon Jan 02 01:03:18 2006 From: Waldo Bastian Date: Mon, 02 Jan 2006 01:03:18 +0000 To: kde-core-devel Subject: Re: KDEinit problem Message-Id: <200601011703.23317.bastian () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113616403915031 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1201261.cqNVOmbCTM" --nextPart1201261.cqNVOmbCTM Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 31 December 2005 16:43, Anders Lund wrote: > On Sunday 01 January 2006 01:19, Waldo Bastian wrote: > > .desktop files have an entry X-DCOP-ServiceType and X-DCOP-ServiceName > > that essentially tell the launcher how the application will register > > itself with DCOP. Once the application has registered in that way, the > > launcher will return successfully. > > > > In general, if the process that gets started exits before the applicati= on > > is registered with DCOP, it assumes something went wrong and returns an > > error. > > > > X-DCOP-ServiceType can have the following values: > > * None - Don't wait for DCOP registration, return success immediate. > > * Unique - Application registers as a unique application > > * Multi - Application registers as name- > > * Wait - Wait till the process exists and return success. > > So I could try setting the type to Wait or None. > > Will that be likely to have any unwanted side effects? Applications that start kate and expect to be able to make dcop calls direc= tly=20 afterwards may fail if kate hasn't registered itself by then. But I suspect= =20 you only want to use this for the special case where you start kate with=20 =2D-use ? Cheers, Waldo --nextPart1201261.cqNVOmbCTM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDuHvbN4pvrENfboIRAm+9AJ43iP/AAj7I7lqMz0bE+fOnuOLV6wCfRRiw D4+RUIAL+ZejfBD+TMp82bs= =uozq -----END PGP SIGNATURE----- --nextPart1201261.cqNVOmbCTM--