Eelco Hillenius wrote:
I didn't notice it before, but there are some convenience methods in ListView for editing (move, delete) list elements. One of the commentors on Matt Raible's blog pointed out: 'and the list page, if you remove one book, and click back , and then click that remove again, it will remove other book'.Yes it should never remove by index...
But i thought we just wanted to keep this for simple cases.
But the our history should restore the ListComponent (what i think it does) But should also restore the model..
Is the model not stored with modelChangePending and ModelChanged with the remove?
So, I propose: - remove methods removeLink and moveUp/DownLink; - fix the library example and anything that uses these links.
Votes please?
For simple things i could be handy for people to have these. I haven't used them myself so they may be removed if it was me.
But we also should look at why the model isn't restored....
johan
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
