Hi,
yes. sometime back we had it working like what you want, but too many users complained that it was not what they wanted so we changed it.
unfortunatly, this pushes the values to the model and forces validation. I think something else is not working with my form, because when a field doesn't validate, this change and other client value changes are lost as well. I'm using forms like I usually do (except there is a panel with a separate compoundpropertymodel in between). Was there some change in how values, which aren't pushed to the model yet, are handled in wicket 1.2?
Ralf ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
