On Thu, Nov 18, 2010 at 12:16 PM, Massimo Lusetti wrote:
> On Thu, Nov 18, 2010 at 12:01 PM, Thiago H. de Paula Figueiredo
> wrote:
>
>> I don't think so. Having more than one event handler method for the same
>> event is something to be avoided anyway.
>
> I don't want to argue, plus I can agre
On Thu, Nov 18, 2010 at 12:01 PM, Thiago H. de Paula Figueiredo
wrote:
> I don't think so. Having more than one event handler method for the same
> event is something to be avoided anyway.
I don't want to argue, plus I can agree with that but the facts are
that now is possible and BTW it was pos
On Thu, 18 Nov 2010 06:42:09 -0200, Massimo Lusetti
wrote:
Wouldn't be nice to have an "ordering" optional parameter to
@SetupRender where you can specify the ordering of execution? ... The
same maybe applies to @BeginRender and friends too...
I don't think so. Having more than one event ha
On Thu, Nov 18, 2010 at 9:42 AM, Massimo Lusetti wrote:
> On Wed, Nov 17, 2010 at 7:13 PM, Howard Lewis Ship wrote:
>
>> I'm sure some combination of the above rules is the explanation for why the
>> method is not being invoked.
>
> I personally have run into a similar situation and I ended havi
On Wed, Nov 17, 2010 at 7:13 PM, Howard Lewis Ship wrote:
> I'm sure some combination of the above rules is the explanation for why the
> method is not being invoked.
I personally have run into a similar situation and I ended having one
@SetupRender annotated method that call various (private) m
f your
> component.
>
> Regards, nillehammer
>
> ----- original Nachricht
>
> Betreff: Re: Re: setupRender not called for components
> Gesendet: Mi, 17. Nov 2010
> Von: Stephan Windmüller
>
> > On Wed, 17. Nov 2010, nille hammer wrote:
> >
>
ender not called for components
Gesendet: Mi, 17. Nov 2010
Von: Stephan Windmüller
> On Wed, 17. Nov 2010, nille hammer wrote:
>
> > > |
> > > |
> > > | public boolean isSetupRender() {
> > > | // Do stuff
> > > | return false;
> > &g
i guess we r missing something in ur code.
Does ur component extend another one? do u have more than one
setupRender in ur component (or parent classes)? could u post the
component code? (please not pieces, it's hard to see the big picture)
On Wed, Nov 17, 2010 at 1:01 PM, Stephan Windmüller
wro
On Wed, 17. Nov 2010, nille hammer wrote:
> > |
> > |
> > | public boolean isSetupRender() {
> > | // Do stuff
> > | return false;
> > | }
> I don't know whether this will solve your problem, but you don't need
> to put in an extra t:if to prevent your component from rendering. I
> sugge
Hi Stephan,
> |
> |
> | public boolean isSetupRender() {
> | // Do stuff
> | return false;
> | }
I don't know whether this will solve your problem, but you don't need to put in
an extra t:if to prevent your component from rendering. I suggest doing the
checks in setupRender and return
10 matches
Mail list logo
