GNUstep - Patches: patch #4638, Cannot use dynamic services unless...
You are not allowed to post comments on this tracker with your current authentication level.
patch #4638: Cannot use dynamic services unless app is already running.
Submitter: | None | ||
Submitted: | Fri 18 Nov 2005 10:45:56 PM UTC | ||
Category: | AppKit | Priority: | 2 |
Status: | Wont Do | Privacy: | Public |
Assigned to: | None | Originator Email: | -email is unavailable- |
Open/Closed: | Closed |
Sun 20 Nov 2005 08:34:04 PM UTC, comment #1: |
Richard Frith-Macdonald <CaS> |
Fri 18 Nov 2005 10:45:56 PM UTC, original submission:
Dynamic services are usable only if the app providing the service is already running, otherwise the app isn't started and the service attempt fails with the error "Failed to contact service provider." This can be tested with any of Terminal.app's dynamic services, for example. The problem seems to be that when the services cache is created by make_services, the ServicePath key is set not to the path of the provider application itself, but rather to the path of the plist containing the definitions for the dynamic services. This patch will set ServicePath to the path of the provider application instead. |
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-11-20 | CaS | Status | None | Wont Do | |
Open/Closed | Open | Closed | |||
2005-11-18 | None | Attached File | - | Added dynamic_services.diff, #5493 | |
Carbon-Copy | - | Added aer --AT-- shaw --DOT-- ca |
Powered by Savane 3.13-758e.
Corresponding source code
I think this problem was caused by a bug launching the application ... now fixed in CVS.
Thanks for the patch, but I think fixing the launching process to use the port it is given is a better solution than changing the path to the service bundle to point to the app providing the service.