Also, some machines don't have sound, and then the wiggly slash is the only indication to the user. At the same time as a beep sounds, the little slash to the left wiggles back and forth, reinforcing the experience and at the same time making it easier to correlate the sound with the list of thread events. The user can now toggle each sound on and off by using the indicated alphabetic key. The way I do it is to have a "secret" key combination call up a window with the list of commands to listen to (see screenshot). Plus, as a matter of fact, it will give you very useful information over the blower.
#DELPHI THREAD AS TIMER PC#
Now you can have him hit the secret hotkey, a few letter keys, then ask him to "please hold the phone close to the PC so I can listen to it". Freakish, but useful.įor instance, you've got this customer really far away who claims that your app has "locked up again". Not so amazingly, it turns out to be really useful. The human sense that is most tuned to detecting relative speeds and really small variations in relationships and tempo is hearing, so I got the idea to make the threads each play their tune, then simply lean back and listen to them. One particular problem is knowing if all threads are still ticking along, since an exception in a thread can easily kill that one thread only. When debugging programs holding a number of threads, it can be real difficult to get an intuitive feeling of how these threads are progressing.
0 kommentar(er)
