Just in general, explicit order of listeners would destroy (current or
future) possibilities for implicit parallelism. Problems with listener
ordering can be solved with event propagation (by creating a nested
element).
Kalle
On Thu, Mar 18, 2010 at 12:27 AM, LiborGMC wrote:
>
> Hi, thanks for
Hi, thanks for responses. I'm using 5.1.0.5. Version 5.2 brings me more pain
than gain ;-).
I think my problem could be somewhere else: both my mixins wired event
handlers to same event "onclick". I don't know JS very well but could be
possible that JS don't keep ordering when notify listeners fo
Depends on what version of Tapestry you are using.
Explicit ordering of mixins is in trunk.
Robert
On Mar 17, 2010, at 3/178:50 AM , Michael Prescott wrote:
As I understand it, mixin order is unspecified. A developer on our
team had
this issue and wound up implementing a custom component, I
As I understand it, mixin order is unspecified. A developer on our team had
this issue and wound up implementing a custom component, IIRC.
Michael
On Wed, Mar 17, 2010 at 11:45 AM, LiborGMC wrote:
>
> Hi there,
> I've implemented two mixins which just add some JavaScript code to action
> onCli
