Per my previous email, I think this is a band-aid over a larger
problem with the DHTML kernel. Please file a bug for the kernel issue.
I also wonder why the debugger needs this extra kludge and a scrolling
window component does not? Are we fooling ourselves?
On Mar 30, 2010, at 12:16, Henry Minsky <[email protected]> wrote:
Change 20100330-hqm-E by [email protected] on 2010-03-30 12:11:19 EDT
in /Users/hqm/openlaszlo/trunk
for http://svn.openlaszlo.org/openlaszlo/trunk
Summary: fix for debugger scrolling output in DHTML
New Features:
Bugs Fixed: LPP-8862
Technical Reviewer: max
QA Reviewer: (pending)
Doc Reviewer: (pending)
Documentation:
Release Notes:
Overview:
Use addTimer instead of callOnIdle to update the scrolling in
debugger output window
Details:
In DHTML, the callback to examine the new scrollheight must be queued
using lz.Timer.addTimer, which uses setTimeout(), rather than
callOnIdle, which uses setInterval.
Tests:
See LPP-8862
Files:
M lps/components/debugger/newcontent.lzx
Changeset: http://svn.openlaszlo.org/openlaszlo/patches/20100330-hqm-E.tar
