Re: Debug windows stops being responsive
2009-12-01 01:29:52 GMT
Can you file a bug report in JIRA with the exact runtime and browser and OS you're using, and if possible which key sequence causes it to get confused?
Running this app will show you what keys the kernel thinks are down. If you find a sequence of key presses which leaves the CTRL key set, please put that info in the bug report.
Thanks very much!
<canvas layout="axis: y; spacing: 10" height="500" debug="true">
<handler name="onidle" reference="lz.Idle">
this.format("Downkeys Array: %w", lz.Keys.downKeysArray);
<handler name="onkeydown" reference="lz.Keys" args="k">
Debug.info("onkeydown: %w, keys: %w",k,lz.Keys.downKeysArray);
<handler name="onkeyup" reference="lz.Keys" args="k">
Debug.info("onkeyup :%w, keys: %w",k,lz.Keys.downKeysArray);
<!-- Copyright 2009 Laszlo Systems, Inc. All Rights Reserved. Use is subject to license terms. -->
Henry,Pressing the CTRL key unlock the Debug window... thanksFrom: Henry Minsky [mailto:henry.minsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: 29 novembre 2009 17:08
Subject: Re: [Laszlo-user] Debug windows stops being responsive
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 sOn Sun, Nov 29, 2009 at 4:49 PM, Ragoran <ragoran-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org> wrote:
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…
hminsky <at> laszlosystems.com