Hi!
I have come up with a work-around not to loose the form components
when having to rebuild a ListView (after .removeAll).
I built a hashmaper for reusing the formComponents and it works ;)
However, I wonder if this could/should be incorporated within the
repeaters - what do you think? Further
Hi!
What is the main difference between repeatingView and listView from
this point of view?
I can see ListView has many features I do not use such a s moving the
rows up and down...
**
Martin
2008/6/11 Al Maw <[EMAIL PROTECTED]>:
> This sort of stuff is definitely possible - people certainly ha
This sort of stuff is definitely possible - people certainly have it working
elsewhere.
If you use setReuseItems(true) you need to call removeAll() if you change
the backing model object.
Timo is probably right that a RepeatingView may be easier to use in this
kind of situation.
Alastair
2008/6
> For some reason, I have often succeeded better with other
> repeaters than ListView (e.g. RefreshingView, DataView) in
> complex situations.
I have postponed studying these, I suspect problems with varying
column counts on rows.
> I think that in a normal submit the same applies -- you have
> t
On Wed, 11 Jun 2008, Martin Makundi wrote:
> I have nested listviews which draw a complex tabular form having
> variable colspans and rowspans depending on the state of the form.
For some reason, I have often succeeded better with other
repeaters than ListView (e.g. RefreshingView, DataView) in
Hi!
I have nested listviews which draw a complex tabular form having
variable colspans and rowspans depending on the state of the form.
I have an Add button to add elements into one of the inner listviews.
Problem:
1. If I have "setReuseItems" true, the HTML table is not rendered
properly (someh
