On Tue, 23 Oct 2012 19:25:52 -0200, bhorvat <horvat.z.bo...@gmail.com>
wrote:
Yes I have, actually it is part of my code, and I have just removed it
since it works the same whether or not it is there
Actually, it works in a different way, I just don't know it would make a
difference when adding an initializer call with
InitializationPriority.LATE, as the ordering of JS function calls is
defined in JavaScript. For rendering additional stuff using a mixin, it
would definitely make a huge difference. Without @MixinAfter, events are
triggered in the mixin first, component later. With @MixinAfter, it's
component first, mixin later.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
