I've fixed this issue by removing the error generation inside the feature drawing code:<br><a href="http://trac.osgeo.org/mapserver/ticket/3171">http://trac.osgeo.org/mapserver/ticket/3171</a><br><br>Best regards,<br><br>
Tamas<br><br><br><div class="gmail_quote">2009/10/14 Thomas Bonfort <span dir="ltr"><<a href="mailto:thomas.bonfort@camptocamp.com">thomas.bonfort@camptocamp.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tamas,<br>
<br>
I'll have a look at this, can you show me the mapfile layer you are using.<br>
This error should only arise if you haven't defined a color or<br>
outlinecolor (and are not using a pixmap symbol).<br>
<br>
regards,<br>
<br>
thomas<br>
<br>
<a href="http://www.camptocamp.com" target="_blank">www.camptocamp.com</a><br>
+33 5 16 57 01 02<br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Tue, Oct 13, 2009 at 23:16, Tamas Szekeres <<a href="mailto:szekerest@gmail.com">szekerest@gmail.com</a>> wrote:<br>
> Daniel,<br>
><br>
> I'm quite sure there's another breaking issue which have been working with<br>
> 5.4. The current version doesn't support rendering transparent pattern fills<br>
> (ie. defining a VECTOR symbol for the pattern). By setting up this kind of<br>
> layers we may ecounter an increased CPU load, and finally get a large error<br>
> message with the following message concatenated several times:<br>
><br>
> msDrawShadeSymbol() General error message. no color set;msDrawShadeSymbol()<br>
> General error message. no color set;msDrawShadeSymbol() General error<br>
> message. no color set;msDrawShadeSymbol() General error message. no color<br>
> set ......<br>
><br>
> Currently I don't have time to provide a test case or fix for that, maybe<br>
> for tomorrow.<br>
><br>
><br>
> Best regards,<br>
><br>
><br>
> Tamas<br>
><br>
><br>
><br>
><br>
> 2009/10/13 Daniel Morissette <<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>><br>
>><br>
>> Hi everyone,<br>
>><br>
>> A quick reminder that 5.6.0-beta4 will be packaged at the end of the day<br>
>> tomorrow. I leave for Sydney very early Thursday morning, so I have to<br>
>> release beta4 before leaving on Wednesday night and cannot push it until<br>
>> later in the week as we did for previous betas.<br>
>><br>
>> I see that our list of open tickets has gone down from 191 to 162. Thanks!<br>
>> Please keep in mind that if we want to stay close to our original release<br>
>> plan and have a first release candidate next week, then beta4 would be your<br>
>> last chance to get non-trivial fixes in before the release candidate.<br>
>><br>
>> Daniel<br>
>> --<br>
>> Daniel Morissette<br>
>> <a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
>> _______________________________________________<br>
>> mapserver-dev mailing list<br>
>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> mapserver-dev mailing list<br>
> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
><br>
><br>
</div></div></blockquote></div><br>