It might be the keyboard handling kernel, it sometimes becomes confused about which keys are down.
Does the "eval" button in the debugger cause output to come back? If so, then that is usually an indication that the kernel is running OK, but the keyboard command processor thinks that some control keys are down when they are not. I can send a little diagnostic which tells you which keys it thinks are down. In the meantime, try hitting the control or option key by itself, to force the keyboard processing code to see a key up, and see if the debugger command processor comes back to life. We've had a long history of difficulty in tracking which keys are actually down, because each browser/OS combination intercepts certain key up or down events before they reach the application, so we have to resort to some heuristics to tell which keys are actually down. Some browsers send key down but not key up for s On Sun, Nov 29, 2009 at 4:49 PM, Ragoran <[email protected]> wrote: > Hi, > > I have developped a data entry form using Laszlo 4.6.1. The form is almost > complete. However, I noticed that the Debug windows stops being responsive > sometimes. I can type a command, but pressing enter will not process it. > The up/down arrow do not scroll the history of the command, but a > Debug.write call from the program will work. > > As everything seems to be working fine with the application, I am wondering > waht could cause such a behavior. Is it a symptom of a bigger problem > (infinite loop…) that will bite me later… > > Thanks > > Ragoran > > > -- Henry Minsky Software Architect [email protected]
