Doe! Can you file a components bug and/or fix?
On 2/4/11 7:46 PM, Henry Minsky wrote:
Yes that helped... turns out the new slider component gets a NaN when
it's min and max values are both zero...
On Fri, Feb 4, 2011 at 10:30 PM, P T Withington <[email protected]
<mailto:[email protected]>> wrote:
If you turn on backtrace wont that explain how yo got there? Note
that you can inspect both the LZX error and the platform error to
get backtraces (LZX and native backtraces). Surely one of those will
yield a clue?
On Feb 4, 2011, at 22:00, Henry Minsky <[email protected]
<mailto:[email protected]>> wrote:
I'm having trouble with the value of some constraints at startup.
I have a slider with these two constraints
<sldr valign="middle"
name="progress" x="64"
value="${classroot.vp.currentTime}" min="0"
max="${classroot.vp.duration}"/>
and I get this error at startup
ERROR @../../lib/slider/library.lzx≈32: TypeError: Result of
expression 'v_$0.split' [undefined] is not a function.
WARNING: CSSDimension: coerced NaN to 0
The view "vp" is a class which has attributes declared as
<attribute name="duration" type="number" value="0"/>
<attribute name="currentTime" type="number" value="0"/>
It seems like the constraint expression is either starting up
with an undefined value, or executing with an undefined value
early on in the startup. Is there a way to figure out where this
undefined value is coming from?
It seems like the code here should never be getting an undefined
value for these attributes. In my component that defines
"currentTime" and "duration", I put a debug print statement into
the setter methods, and they never showed an 'undefined' value
being passed.
--
Henry Minsky
Software Architect
<mailto:[email protected]>[email protected]
<mailto:[email protected]>
--
Henry Minsky
Software Architect
[email protected] <mailto:[email protected]>
