CellTable renders itself in a rendering loop, which means that you can make multiple synchronous changes to the range and/or data but only render once at the end of the synchronous changes. However, the table isn't designed to handle the case where user code actually modifies the table within the rendering loop.
The main things that can cause this are the following:
- Modifying the CellTable from within Cell#render()
- Overriding CellTable#renderRowValues() and modifying the CellTable from within it
- Trying to access an Element in CellTable from either of those methods
Are you doing any of these? The code is somewhat complicated because its optimized for performance and has some special cases. Its certainly possible that there are subtle bugs.
Thanks,
John LaBancajlabanca@google.com
On Mon, Jan 31, 2011 at 1:50 PM, zixzigma <zixzigma@gmail.com> wrote:
I am getting this exception more and more now.
I am not using a Date type,
but I manipulate the "range" the table is showing using table.setVisibleRange.
My problem is that I don't understand what exactly is that I am doing wrong,
and how to change my code to avoid this exception.
in other words, what is this Exception "Really" saying ?
if it has to do with Range, under what circumstances this exception occur
so that I can guard against it.
Thank You
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment