I'm not sure that this implementation of CycleBinding is fit for core as it uses a thread local so nested bindings won't work (I don't think)
I don't think that the following would work. <t:loop ...> <div class="${cycle:a,b}">... <t:loop ...> <div class="${cycle:d,e}">... </t:loop> </div> </t:loop> I'm thinking that ComponentResources.storeRenderVariable() and componentResources.getRenderVariable() might be a better fit than ThreadLocal? -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-have-every-second-value-in-the-t-loop-different-tp5714278p5714306.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org