bastian at kde.org
Mon Jan 2 01:03:18 GMT 2006
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 application
> > 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-<pid>
> > * 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 directly
afterwards may fail if kate hasn't registered itself by then. But I suspect
you only want to use this for the special case where you start kate with
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel