listItems is the array of renderers. In theory, every visible row should
have at least one renderer, so listItems[rowIndex][0] cannot be null for
any visible row.
In the tree, in this code, theoretically you've clicked on the row that is
rowIndex to close away its children so there should be a renderer.
But if this code is running from a programmatic call to close a node then
you might be catching it in some condition where in 4.10 some sizing is
slightly different an there is no renderer at that row.
-Alex
On 9/25/13 8:54 AM, "Miguel Ferreira" <miguel.cd.ferre...@hotmail.com>
wrote:
>Hi all,
>This week i am updating the sdk for the version 4.10 i had problems
>before but was i needed to update parsley version.
>After that all went fine.
>In this moment i get a error in one tree and i just don't know if is
>related with the sdk or not.Because i have a tree working and other not.
>Even so this error i think we could prevent it:
>so in the component tree.as
>on the line 1962 we have this code
> // figure out how much space was consumed by the rows that are going
>away for (i = rowIndex; i < rowIndex + rowsToMove && i <
>rC; i++) { maxDist +=
>rowInfo[i].height; // retain a reference to the rows
>going away rowList.push({item: listItems[i][0]});
> tmpMask = makeMask(); tmpMask.x = xx;
> tmpMask.y = listItems[rowIndex][0].y;
>tmpMask.width = ww; tmpMask.height = maxDist;
> listItems[i][0].mask = tmpMask; }
>and this line tmpMask.y = listItems[rowIndex][0].y;
>don't have the properties we have a rowindex of one but no content for
>that so is throwing a error of:Error #1010: A term is undefined and has
>no properties.
>Some ideas?
