I suspect a deeper issue, perhaps in LzText?
Note:
lzx> Boolean(0)
false
lzx> Boolean('0')
true
lzx>
Is this another case where we have a setter that is not enforcing the
type contract of its slot?
I'm concerned that the generic setText does not coerce to a string.
Although this appears to be handled in the kernel, it means that the
generic text slot will not be of type string. Could you try hoisting
the type enforcement up from the kernel to the generic code?
Max, what do you think?
On 2007-02-08, at 04:25 EST, J Crowley wrote:
Change 20070208-jcrowley-C by [EMAIL PROTECTED]
on 2007-02-08 04:09:03 EST
in /Users/jcrowley/src/svn/openlaszlo/legals-two/lps/components/lz
Summary: DHTML:Missing minimum value on the slider
New Features:
Bugs Fixed: LPP-3007
Technical Reviewer: max
QA Reviewer: promanik
Doc Reviewer:
Documentation:
Release Notes:
Details: This was actually a problem with slider.lzx. For some
reason,
in DHTML, when the minimum value was "0", when it set the text
corresponding to the minimum value, it was, I think, not
recognizing it as a string, and seemed to be setting text to
null. Adding a +'' to where it sets the text makes it show up
appropriately. Same goes for the text corresponding to
maxvalue.
Tests: Ran the OL Explorer example, and a modified version thereof.
Noticed that the values showed up when zero, and otherwise
continued to behave as expected.
Files:
M slider.lzx
Changeset: http://svn.openlaszlo.org/openlaszlo/patches/20070208-
jcrowley-C.tar
