Xcode build success/failure sound paths not working

[GoogleCodeExporter]

What steps will reproduce the problem?
1. select Xcode in Secrets, then select an aiff (e.g. from ~/Library/Sounds), 
right click and get POSIX path, paste to Secrets build success or 
failure text field (I used Temple.aiff)
2. ditto HFS path (I used Uh oh.aiff which I believe originated in OS 9. In any 
case, Quicklook makes the sound)
3. start Xcode, build a project, either successfully or insert a source code 
error

Variations I tried: double-quote path, \  quote spaces in path (e.g. Macintosh\ 
HD:).  Haven't read source, do you evaluate path using a 
shell? Press Return or not press return in text field. Also, quit System 
Preferences/not quit before starting Xcode. In all cases I quit Xcode 
before editing in Secrets. Did not log out/in.

What is the expected output? Wanted to hear a beep (in Quicklook I could hear 
sound from same aiff) on success or failure of build. 

What do you see instead? Normal build or fail, as though I had not set up in 
Secrets.

OTHER NOTE: after restarting System Preferences, these fields were empty, even 
though I had quit SP with paths in the fields.. I note that 
Indent on paste was correctly remembered between launches, and permissions:

bayesMacBook: ls -l com.apple.Xcode.plist
-rw-------  1 bayes  bayes  38729 Mar  3 08:54 com.apple.Xcode.plist

so I don't thinks it's a permissions problem, though I didn't grovel through 
the plist to see if/where the build sound preferences were 
stored.

What version of the product are you using? Secrets 1.0b16, Xcode Version 3.0, 
Component versions Xcode IDE: 921.0, Xcode Core: 921.0, 
ToolSupport: 893.0

On what operating system? 10.5.2, no Haxies, etc


Please provide any additional information below.
See comments above on procedure and evidence

Original issue reported on code.google.com by scottba...@kdn.biglobe.ne.jp on 3 Mar 2008 at 12:02

[GoogleCodeExporter]

What do you see instead? I should have said "does not beep, whether success or 
fail, as though..."

Original comment by scottba...@kdn.biglobe.ne.jp on 3 Mar 2008 at 12:07

[GoogleCodeExporter]

try it now? It was incorrectly set to specify that value for all users.

Original comment by j...@gmail.com on 3 Mar 2008 at 1:24

• Changed state: Fixed