You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Iain Miller (JIRA)" <de...@velocity.apache.org> on 2010/08/26 20:13:55 UTC

[jira] Created: (VELTOOLS-128) LoopTool doesn't sync correctly

LoopTool doesn't sync correctly
-------------------------------

                 Key: VELTOOLS-128
                 URL: https://issues.apache.org/jira/browse/VELTOOLS-128
             Project: Velocity Tools
          Issue Type: Bug
          Components: GenericTools
    Affects Versions: 2.0
         Environment: Velocity Tools 2.0, Velocity Engine 1.6.4
            Reporter: Iain Miller


When using LoopTool, it doesn't appear to sync correctly, starting "one in" on the second list, and also missing the last value from the second list.

Running the example from the documentation, without the stop():

  #set( $list = [1..7] )
  #set( $others = [3..10] )
  #foreach( $item in $loop.watch($list).sync($others, 'other') )
    $item -> $loop.other
  #end

produces:
    1 -> 4
    2 -> 5
    3 -> 6
    4 -> 7
    5 -> 8
    6 -> 9
    7 -> $loop.other


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Resolved: (VELTOOLS-128) LoopTool doesn't sync correctly

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
     [ https://issues.apache.org/jira/browse/VELTOOLS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bubna resolved VELTOOLS-128.
-----------------------------------

    Fix Version/s: 2.0.x
                   2.x
       Resolution: Fixed

Ok, i've mostly fixed these problems.  I believe there are still some issues with last synced items in outer watched and synced loops when an inner loop has finished rendering, but i don't know that there's any reasonable way to fix those, at least not without undesirable side-effects.  The reality is that LoopTool is attempting some fairly audacious stuff for a tool and can only support a certain level of complexity.

So all reading this who wish to do complex nesting, watching and syncing with LoopTool had best push their insanity out of their templates.  Or ask me and i'll tell you some even... uh... "loopier" in-template solutions that just occured to me.  :)

> LoopTool doesn't sync correctly
> -------------------------------
>
>                 Key: VELTOOLS-128
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-128
>             Project: Velocity Tools
>          Issue Type: Bug
>          Components: GenericTools
>    Affects Versions: 2.0
>         Environment: Velocity Tools 2.0, Velocity Engine 1.6.4
>            Reporter: Iain Miller
>             Fix For: 2.0.x, 2.x
>
>
> When using LoopTool, it doesn't appear to sync correctly, starting "one in" on the second list, and also missing the last value from the second list.
> Running the example from the documentation, without the stop():
>   #set( $list = [1..7] )
>   #set( $others = [3..10] )
>   #foreach( $item in $loop.watch($list).sync($others, 'other') )
>     $item -> $loop.other
>   #end
> produces:
>     1 -> 4
>     2 -> 5
>     3 -> 6
>     4 -> 7
>     5 -> 8
>     6 -> 9
>     7 -> $loop.other

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org