If an ajax grid does work please open an issue on google code so I can check it and we can fix it. I cannot reproduce your problem otherwise.
On Oct 11, 1:12 pm, apple <[email protected]> wrote: > Surely there must be a solution to this? It does not seem logical to > have a component that is arbitrarily restricted to one per page? > > iframe is not a good solution. And I don't think LOAD with ajax works > with multiple grids and pagination - certainly it does not work in my > application even after the recent fix in trunk. I have got multiple > grids to work with LOAD and no ajax, including the add/view/edit but > not pagination. > > Surely there are many possible solutions to this without compromising > the URL benefits you mention. For example you could include a "gridid" > in request.args or request.vars; maybe also save the grid parameters > in session. > > On Oct 11, 3:44 pm, Anthony <[email protected]> wrote: > > > > > > > > > On Tuesday, October 11, 2011 9:49:51 AM UTC-4, stefaan wrote: > > > > (workaround: e.g. use iframes, or design a better UI that doesn't need > > > two grids in one view ;) > > > Using ajax components might be better/easier than iframes.
