The bug is about setVisible() method which does not work on button (and not
only) components when using ajax updates.
Detailed description:
I have a DataView. Each line contains a description (Label component), a
configuration select (DropDownChoice component) and a download button
(Button component). When user changes the configuration from the
DropDownChoice component, depending on the selected configuration - the
download button visibility must be changed. Here is the snippet of code:
protected void onUpdate(final AjaxRequestTarget target) {
//find somehow my button using relative path
Button button = ...;
button.setVisible(false);
target.addComponent(button);
}
This code does not perform the expected result. Interesting is that if
instead of button, I try to change the visibility of a DropDownChoice
component - it works!
I cannot understand why it behave so different. Can you explain me? Is it a
bug? Am I using a wrong approach?
Thank you!
--
View this message in context:
http://www.nabble.com/Wicket-1.2.4-bug-%28-%21-%29---changing-visibility-of-a-button-using-ajax-tf3242268.html#a9013073
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
