<br><br><div class="gmail_quote">2010/11/9 Lime, Steve D (DNR) <span dir="ltr"><<a href="mailto:Steve.Lime@state.mn.us">Steve.Lime@state.mn.us</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Let me think on that. Actually I’d like to remove whichShapes()
from mapscript and force users through a query method. I don’t think</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">it’s worth the headache to support that method. I should have
never added it… </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p></div></div></blockquote><div><br>I like these methods whichShapes and nextShape (probably I was the one who has motivated to add ;-) because I'm not aware of any alternative way in mapscript to provide raw access to all shapes without requiring to build up a result cache with all of the retrieved results.<br>
<br>Tamas<br> </div></div>