Re: Button not visible, except that it is...
Nevermind, it's because he didn't have that higher panel in the target for that event. So he set the visibility to false without realizing it, and didn't add it to the target. Mystery Solved. Thanks as always for the quick response. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567p4678576.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Button not visible, except that it is...
The isVisibleInHierarchy() method returns false. Stepped into that and realized that my co-worker was setting a parent panel false in a panel further up the hierarchy in the onConfigure of a behavior, which fires once at page load and again after the button click that makes this other button/panel visible. But that code hard-coded it to false. It should have rendered the whole panel invisible I would think. Which is not what we want, but I am confused why the panel rendered as visible. onConfigure() javadoc says it fires before render. So that is confusing to me. But we definitely have the problem figured out. Any idea why the panel rendered as if visible? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567p4678574.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Button not visible, except that it is...
On Mon, Aug 21, 2017 at 5:47 PM, Entropy wrote: > We have a form that underwent some re-writing. After the changes, a button > starts throwing the below exception. The button is in a panel that starts > invisible but is made visible later. In the event that makes it visible we > logged out the button's isVisibleInHierarchy() and it was false at the > beginning of the method, true at the end. And the button DID render on the > page. > > So if wicket thought the button was visible by it's own method, and chose > to > render it, why does it later think it's not visible in the very next event? > We are not overriding any isVisible() methods in the page. Any ideas? > Just put a breakpoint at Form.java:456 and see why it thinks it is invisible. Most probably some of its parents is not visible if the button itself is. > > org.apache.wicket.WicketRuntimeException: Submit Button > radioWmc2:radioWmc2Step2:btnResResume > (path=form:radioWmc2:radioWmc2Step2:btnResResume) is not visible > at > org.apache.wicket.markup.html.form.Form$2.component(Form.java:456) > at > org.apache.wicket.markup.html.form.Form$2.component(Form.java:437) > at > org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144) > at > org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > at > org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > at > org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > at > org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123) > at > org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:860) > at > org.apache.wicket.markup.html.form.Form.findSubmittingButton(Form. > java:435) > > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Button not visible, except that it is...
We have a form that underwent some re-writing. After the changes, a button starts throwing the below exception. The button is in a panel that starts invisible but is made visible later. In the event that makes it visible we logged out the button's isVisibleInHierarchy() and it was false at the beginning of the method, true at the end. And the button DID render on the page. So if wicket thought the button was visible by it's own method, and chose to render it, why does it later think it's not visible in the very next event? We are not overriding any isVisible() methods in the page. Any ideas? org.apache.wicket.WicketRuntimeException: Submit Button radioWmc2:radioWmc2Step2:btnResResume (path=form:radioWmc2:radioWmc2Step2:btnResResume) is not visible at org.apache.wicket.markup.html.form.Form$2.component(Form.java:456) at org.apache.wicket.markup.html.form.Form$2.component(Form.java:437) at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144) at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123) at org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:860) at org.apache.wicket.markup.html.form.Form.findSubmittingButton(Form.java:435) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
