Ron Baum writes:

I am using dtml-in's batch features and noticed that I am getting an overlap of the last item to the top of the next batch. I changed the overlap attribute to 0 and I still get the overlap. Is there anything else that I need to do to make this work? I expect this is a design bug in in's batching.

The "start" attribute is "1" based, i.e. if you say "start=1" the batch starts with the first element. However, "next-sequence-start-index" is "0" based. This implies, if you use "query_start=&dtml-next-sequence-start-index;" the next batch will start with the last element from the current batch. You can get rid of this by using query_start=<dtml-var "_['next-sequence-start-index'] + 1"> Of course, I think the need to do it in this weird way is stupid. "in" should define "next-sequence-start-number" (which would be "1" based)! Dieter