Subject: Re: [xsl] updating xsl:variable inside the loop From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 29 Jan 2004 14:08:30 GMT |
If I use this condition <xsl:if test="@rowindex=preceding-sibling::*/@rowindex"> presumably then you want a slightly different condition. You didn't say what criterion you want to test, only showed some xsl code that shoul dhave generated an error about rebinding a local variable. It isn't ever easy to guess from wrong code what you wanted, actually I suppose you wanted to know if the immediately preceing attribte is less (or if there isn't such an attribute) <xsl:if test="not(preceding-sibling::*[1]/@rowindex) or preceding-sibling::*[1]/@rowindex < @rowindex "> -- http://www.dcarlisle.demon.co.uk/matthew ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] updating xsl:variable ins, Arulraj | Thread | Re: [xsl] updating xsl:variable ins, Arulraj |
Re: [xsl] updating xsl:variable ins, Arulraj | Date | RE: [xsl] Empty object, Strolia-Davis Christ |
Month |