Hi,
On Tue, Oct 25, 2011 at 11:10 AM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote:
> I don't think those are called on Ajax updates.
SetupRender and the rest of the render phase events are called if the
component is inside the block that updates the zone (if it's the zones body,
than inside the zone). They aren't called on the page containing the zone.
> I use @SetupRender now and it only works before the ajax update.
>
>
> On Oct 25, 2011, at 5:00 AM, Steve Eynon <steve.ey...@alienfactory.co.uk>
> wrote:
>
> > Could you use ... ?
> >
> > @InjectContainer
> > private ClientElement container;
> >
> > void afterRender() {
> > container.getClientId();
> > }
> >
> > Steve.
> >
> > On 25 October 2011 16:53, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
> >> I guess I now have an infamous situation,
> >> a component inside a zone, which has a mixin.
> >>
> >> The mixin gets the client ID of it's component, which works great, until
> the zone gets updated.
> >>
> >> The zone now has random-ish client ID for the component. How do I fix
> my mixin so it gets the new client ID?
> >>
> >> Thanks
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> >> For additional commands, e-mail: users-h...@tapestry.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
