If we would make another default then the other camp will start complaining, and changing that breaks a lot others
Maybe what we could do is trying to detect things, but i dont like that magic to much. Or have a subclass of listview with a very good decriptive name that has the default reuse.. On 1/17/08, Jan Kriesten <[EMAIL PROTECTED]> wrote: > > Hi Martin, > > > Again, what you are doing is a corner case. The default for listview > > is to show data which updates automatically when refreshed if the > > model provides an updated list. This is the way it is intended, > > designed and documented. > > I have seen the 'Warning' sign on ListView - no question. And I did quite a > few > things with ListView. > > The logic I'm missing: You expect ListView being used (mostly) for read-only > lists. When lists are read-only, why can't those entries being reused? > > In fact, in the case I described, the list being used was stable, the > containing > Panels just were ajaxified (they contained ListViews as well). > > Since there are regularly questions with IRC as well as on the List (mostly > concerning ListViews with Forms I admit), the default seems not to fit > expectations in many situations. I was well aware of the Form-problems with > listview, but that it would break fallback-behavior I really missed (I now > would > have this in mind, too, of course). > > best regards, --- jan. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
