Um, er... It was a relatively arbitrary decision. By that I mean I didn't have any symbolization use cases that required more than 3, let alone 5. So to bump it you'd have to recompile. There should be virtually no penalty for going to a value of say 10.
That said, you are only describing a case with 3 styles. If that's the case then the issue is why are you hitting the limit at all? (and the limit of 5 is protecting you). Are you actually creating classes with more than 5? Steve >>> Ludwig Max Brinckmann <[EMAIL PROTECTED]> 7/13/2006 10:53:12 AM >>> I am using Mapserver through Primagis, which uses mapserver as rendering engine. I have a road network which I want to display at varying zoom levels in different ways, with the roads rendered by stacking styles on top of each other: eg. a wide black line on top of which comes a narrower yellow line on top of which comes a narrow black line, which overall gives the impression of a divided highway as we know it from paper maps. I do this at varying zoom levels, but then when rendering I get the message MapServerChildError: insertStyle(): Child array error. Maximum number of class styles, 5, has been reached which comes from classobject.c. Obviously, I can change this in map.h and recompile. But is there a good reason for such a low maximum? Is it there to protect people from their own errors or is there a significant performance penalty or some such? Ludwig
