my fix was
if someone needs it ..
Regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Question-or-feature-request-afterOnInitialize-tp3732520p3743198.html
Sent from the Users forum mailing list archive at Nabble.com.
Yes, now I understood. :-) Thanks
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Fri, Aug 12, 2011 at 2:56 AM, armandoxxx armando@dropchop.comwrote:
@IGor: I figured it out .. no need for new features.
@Bruno: if you cann onAfterInitialize() in onInitialize() you can't be
Igor: thank you for your reply and your solution. Could you please discuss
this case with other developers and let me know what they think? In my
opinion framework should make my job easier not force me to do workarounds
to get what I need. Just a thought.
Martin: thank you :D
Kind regards
On Thu, Aug 11, 2011 at 4:35 AM, armandoxxx armando@dropchop.com wrote:
Igor: thank you for your reply and your solution. Could you please discuss
this case with other developers and let me know what they think?
this is the place where the developers discuss things. if any of them
want to
Isn't this correct?
onInitialize() {
super.onInitialize();
... // whatever I put here would be the same as overriding
onAfterInitialize();
}
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:35 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
On Thu, Aug
@IGor: I figured it out .. no need for new features.
@Bruno: if you cann onAfterInitialize() in onInitialize() you can't be sure
all components on the page we're
initialized()
Regards
Armando
--
View this message in context:
Hey guys ...
With wicket 1.5 we got events. So far so good but I got a case where i'm
missing after on initialize method call.
I have lot's of panels on my page, and I create them in onInitialize() code.
But I need to send a 1 time event after all components are initialized.
- problem #1: If
Hi Armando, the problem #1 is rather about not have the entire
component tree connected already. onInitialize is called when the
component is aware of its path to page, at this moment, a triggered
even will not reach new nodes addition in the component tree.
On Wed, Aug 10, 2011 at 7:23 AM,
You almost found it yourself.
Use onBeforeRender() + hasBeenRendered() instead of your custom flag.
On Wed, Aug 10, 2011 at 1:23 PM, armandoxxx armando@dropchop.com wrote:
Hey guys ...
With wicket 1.5 we got events. So far so good but I got a case where i'm
missing after on initialize
@pedro I know. That's why I didn't put the event call in onInitialize()
method ;)
@martin: I if use on before render .. my event would be triggered everytime
my component renders .. so if I want 1 time event after the component is
initialized I have to use somekind of a flag for this event to be
we cant keep building these things because eventually someone will ask
for onAfterAfterInitialized() and so on. what we can do is make it
easy for you to build your own. you can create your own
IComponentOnBeforeRenderListener that checks if the component being
rendered is a page and if it is
MyPage.java:
protected void onBeforeRender() {
if (!hasBeenRendered()) {
send(...);
}
super.onBeforeRender();
}
On Wed, Aug 10, 2011 at 8:18 PM, armandoxxx armando@dropchop.com wrote:
@pedro I know. That's why I didn't put the event call in
this will get called more than once for a component that starts out
and remains invisible for a while.
-igor
On Wed, Aug 10, 2011 at 10:25 AM, Martin Grigorov mgrigo...@apache.org wrote:
MyPage.java:
protected void onBeforeRender() {
if (!hasBeenRendered()) {
send(...);
That's why I put MyPage.java: above it.
I've never tried to make the page invisible :-)
On Wed, Aug 10, 2011 at 8:32 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
this will get called more than once for a component that starts out
and remains invisible for a while.
-igor
On Wed, Aug 10,
what if a component is added later during a panel swap?
-igor
On Wed, Aug 10, 2011 at 10:34 AM, Martin Grigorov mgrigo...@apache.org wrote:
That's why I put MyPage.java: above it.
I've never tried to make the page invisible :-)
On Wed, Aug 10, 2011 at 8:32 PM, Igor Vaynberg
Now I'm convinced we need onAfterInitialize() :-)
On Wed, Aug 10, 2011 at 8:42 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
what if a component is added later during a panel swap?
-igor
On Wed, Aug 10, 2011 at 10:34 AM, Martin Grigorov mgrigo...@apache.org
wrote:
That's why I put
16 matches
Mail list logo
