Hi, I would advise you to control these via CSS rather than implementing server level logic. Though its possiblle writing server level logic to achieve client UX objectives is just bad practice in my opinion. .. BTW thats the reason why you are struggling :)
Here is how I'd prefer to solve any UI/US issue. Use an *AbstractBehavior* like *SimpleAttributeModifier*, to add a class to represent some state. Then via simple CSS, simple control the UI state as you please. This ensures the server is communicating necessary information about STATE to the page, and the CSS translates the STATE to any UI logic or Action you see fit. ----- Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/DataTable-Selected-Row-And-Paging-tp4673621p4673623.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
