Re my second point (two page display containers), perhaps another approach would be to let users specify optional separate top and bottom containers. That could also remove the need for positionFixed, if one assumes a bottom container always needs to be moved.
On Aug 19, 4:15 pm, Chris <[EMAIL PROTECTED]> wrote: > Simple, I think. I tried putting the page view control at the top of > my table and setting positionFixed to false, but it still jumped to > the bottom when I changed page size. > > Either savePage() or fixPosition() should check positionFixed before > moving the page number container. > > if fixPosition() checks positionFixed, then the check on positionFixed > inside renderTable() can be removed,so that seems like the better > change. > > Or did I miss the point? > > What I'd actually like even better is allowing a page view control at > both the top and bottom of the table.
