After looking at your example and digging through the stack a little more, I came to a different conclusion!
You seemed to have inadvertently discovered a bug inspired by my example, but my problem was actually completely different after I thought of it for a second: A few posts back, I mentioned a dialog box that contains checkboxes that represent columns in the database. This dialog box instance is cached as a member object of my CCItemTable class. Without thinking, I stuck this object in the dispose method of my CCItemTable class. So what's happening is: when I go to refresh the table, the table's dispose method is called, which throws away the dialog box. Since all window objects are actually children of the root page, an error occurs when the page is rendered because it's trying to render a child that's been disposed by the table. However, why Qooxdoo 1.0.1 didn't complain about this is a mystery to me. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Problem-with-refreshing-remote-table-tp5005384p5016419.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
