I can confirm this. It took me a few days of debugging before I found out :(
Another solution is to just replace the inmethod grid with a freshly
created instance after data changes. You can share the DataSource, and
you may have to copy over the set of selected items.
Regards,
Erik.
Poi
On Mon, 15 Mar 2010 16:06 +0100, "Thierry Peng" wrote:
> Pointbreak schrieb:
> > On Mon, 15 Mar 2010 15:06 +0100, "Thierry Peng" wrote:
> >
> >> Pointbreak schrieb:
> >>
> >>> The public interface of the inmethod DataGrid/DefaultDataGrid does not
> >>> seem to provide functionality to exp
Pointbreak schrieb:
On Mon, 15 Mar 2010 15:06 +0100, "Thierry Peng" wrote:
Pointbreak schrieb:
The public interface of the inmethod DataGrid/DefaultDataGrid does not
seem to provide functionality to expand the number of rows after an
ajax-call that e.g. adds data to the underlying data
On Mon, 15 Mar 2010 15:06 +0100, "Thierry Peng" wrote:
> Pointbreak schrieb:
> > The public interface of the inmethod DataGrid/DefaultDataGrid does not
> > seem to provide functionality to expand the number of rows after an
> > ajax-call that e.g. adds data to the underlying datasource. Is there a
Pointbreak schrieb:
The public interface of the inmethod DataGrid/DefaultDataGrid does not
seem to provide functionality to expand the number of rows after an
ajax-call that e.g. adds data to the underlying datasource. Is there a
way to tell the DataGrid that the underlying datasource may have
ch
