![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: More Smalltalk questions |
KevinCole Member |
![]() ![]() ![]() Hi. I have a few questions about home-grown Tools. I'm working with a researcher studying hearing and speech, who would prefer to keep our stuff under wraps until we're ready to publish. So, she's asked me not to post our files here. (After the experiment has finished and the results are public, I think she's very open to releasing the Kyma code to the general public.) Unfortunately, it's getting to the point where I cannot easily make a stripped-down version of the tool in order to illustrate the problems. So I ask you to bear with me. 1) Is it possible to get a coherent printout of the Smalltalk code in a Tool? Working in that tiny window is a bit of a nuisance. 2) What's the best way to study/debug unintended side-effects? Specifically, we have a Sound that has a very precise duration (1800 ms). When tested alone, or in a compiled sound grid, it is within 2 ms of the intended length. However, when playing through a tool I've designed, somewhere, I have an OCCASIONAL unintentional triggering of a state change, which sometimes cuts off the sound too soon. At least, that's my guess as to why it cuts out too quickly. I don't yet know what conditions trigger the stopping of the sound. Thanks for any help. P.S. I'm not a Smalltalk or OOP programmer, so be gentle with your answer(s). IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.