:: Forum >>

AW 2.5 and setCurrentRow and setScrollTop

I just upgraded my application from AW 2.0.2 to AW 2.5 and so far I've only run into one problem. Several of the screens in the application will display an iframe containing a grid and the grid needs to be displayed with a certain row selected and in the middle of the visible section of the grid and the first column selected. Through trial and error I came up with code such as the following example that worked just fine in AW 2.0.2:

obj.setRowCount(7263);
obj.setColumnCount(16);
obj.setCellEditable(true);
obj.setCellModel(table);
obj.setSelectedRows([5795]);
obj.setCurrentRow(5795);
obj.setScrollTop(104094);
obj.setScrollLeft(0);
obj.setSelectedColumns([0]);


That same code generates an error in AW 2.5: "nextSibling is null or not an object, line 92, char 2755". I found that if I commented out the setCurrentRow and setScrollTop function calls that the error went away (but the correct row was no longer selected and displayed). Is there a different way to accomplish the same goal as the above code that is more compatible with AW 2.5?
Randall Severy
Friday, December 7, 2007
/javascript.forum.21348.6/version-2-5.html
Flaffer
Saturday, December 8, 2007
Flaffer,

Thanks for the reference, I had read those other AW 2.5 posts, but didn't catch the reference to the "nextSibling is null" error. I tried the workaround outlined in that thread and while it works to some degree it is an ugly kluge that I'd like to avoid. In my case, I'm trying to set the current row before the grid is displayed, so I need to account for the time it will take to display the grid in setting the timeout. I found that I had to set it to 1000 milliseconds to make the error go away. And if the application is being used on a computer even slower than mine, it would need even more time. And with the timeout, it means that the grid is first displayed with row 0 displayed and then is redrawn with the row I wanted selected in the first place, which looks like the kluge that it is. So I'm still hoping to find a better way of doing this than the timeout workaround.
Randall Severy
Sunday, December 9, 2007
I believe I have found what triggered 'nextSibling' bug and I am working on a fix right now. Please give me 1-2 days for more testing.
Alex (ActiveWidgets)
Sunday, December 9, 2007
Randall,

Sure, I only suggested this as a workaround did not expect us to live with this forever, sounds nice Alex.
Flaffer
Monday, December 10, 2007
I believe it is fixed now - please check the corrected code:
/general.bugs/2-5-1.html
Alex (ActiveWidgets)
Monday, December 10, 2007
fixed in AW 2.5.1
Alex (ActiveWidgets)
Tuesday, December 11, 2007

This topic is archived.


Back to support forum

Forum search