|
|
|
|
OOFILE | Downloads | Purchasing | Press | Services | Company Information | Soapbox | References | F.A.Q. | HOME |
|
Audible Debugging |
|
This was prompted by an interesting article in New Scientist discussing
research translating program structure into audible renditions I've used audible debugging twice in the past 10 years. On one Macintosh system for billing, which had to synchronise data between two computers, I added softly spoken phrases to tell me who was sending data. The users requested I leave this debugging feature in because it let them know if their flaky network was down and they felt more confident literally hearing the computers talk to each other. I've also used different sequences of tones when debugging stereoscopic movie rendering software (http://www.ddd.com) as the easiest way to tell me what parts of the movie were arriving in what order, without interfering with the screen. The current (Pro 8) version of CodeWarrior includes audible debugging in two forms as part of their EventPoints. You can set a simple Sound Point to play a sound when a line of code is reached, or choose a Log Point to speak your choice of text (as well as log it to a file). |
