Yes, that would work...but only for me. I am making a macro for general  
consumption.

But given your response I see there is essentially no hope of changing  
this in any way.
As a fellow software developer I understand; low request features/changes  
which are not bugs are not very high sprint priorities.
As a user, it sucks, and I was actually surprised that there even was such  
a limit.

I will adaptively disable the portion of code responsible for generating  
the mass of extra components; while not an optimal solution, it is a  
solution none the less.

I would like to thank you and the rest of the pov team for your continued  
development; I would not be where I am today were it not for pov-ray. :)

Merry Christmas!

On Sun, 26 Dec 2010 18:52:48 -0500, Chris Cason  
<del### [at] deletethistoopovrayorg> wrote:

> On 27/12/2010 10:48, [GDS|Entropy] wrote:
>> That limit really puts a hamper on what I am doing...
>
> you're welcome to build your own binary.


-- 
Ian McDonald
Lean Agile .NET 4.0/MVC
Senior Application Architect,
Developer and Security Analyst

Post a reply to this message