Provide first level support for playing a sound at a breakpoint

Originator:markos
Number:rdar://16341784 Date Originated:17-Mar-2014 03:26 PM
Status:Duplicate Resolved:
Product:Developer Tools Product Version:5.1
Classification:Enhancement Reproducible:Not Applicable
 
Summary:
Even though Xcode supports playing a sound on a breakpoint, it takes 5 steps to set up one. This enhancement should add support to add a sound breakpoint in one step with only a keystroke/action.

Steps to Reproduce:
1. Click to set the breakpoint
2. Edit breakpoint
3. Select “Sound” action
4. Select the sound
5. Select “Automatically continue after evaluating”


Expected Results:
Be able to set a sound breakpoint with one click.
Be able to assign a different sound breakpoint with one click.

Actual Results:


Version:
Xcode 5.1
Build version 5B130a

10.9.2

Notes:
A straight forward implementation would be to add Xcode support for a custom keyboard shortcut to assign a sound.

An enhanced implementation could offer a "Compose" view to be able to compose a tune by assigning sounds across a codebase.

A related talk was given at NSConference 6
https://speakerdeck.com/qnoid/sound-debugging-nsconference-2014


Configuration:


Attachments:

Comments

Duplicate of 3422737 (Open)

Apple Developer Relations18-Mar-2014 11:06 PM

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.

If you have any questions or concerns, please update your report directly here: http://bugreport.apple.com/.


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!