|
![](/i/fill.gif) |
In article <qqm### [at] schlatt fmi uni-konstanz de>, Thomas
Willhalm <tho### [at] willhalm de> wrote:
> Mmmh, I don't like the idea of saving a temporary file that has several
> times the size of the final image.
It is better than trying to keep it all in RAM!
> Perhaps you should consider to apply the filter on the fly. I know
> that you need more than one pixel a time for several of the
> exististing and proposed filters. Perhaps it is possible to determine
> which one you need and forget the others.
This would probably be quite difficult...currently, a filter can access
any position in the data "images". To do this, you would have to do it
during rendering, and would probably have to place restrictions on the
possible things the filters can do. Either that, or recalculate the data
as it is required...which could get extremely slow. Most people have
enough disk space.
And what is wrong with a temporary file anyway?
--
Christopher James Huff - Personal e-mail: chr### [at] yahoo com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |