What I want is to write some macros which keep
track of the resolutions of meshes which were
saved to disk.

Here's an example:
I've designed some cloth-mesh with a resolution of 50x50 Nodes.
I'd use the system as follows:
Create an identifier named "cloth_res", *attaching* "cloth.dat" as
filename and <50,50> as vector to it using the system.
I'd render the scene, those settings will be saved to disk.

The second time I trace the image, the system will check the
formerly saved stats. It returns "true" if I want to load "cloth.dat"
with a resolution of 50x50, since these were the values I've
used before.
If I'd try to trace the image with a new resolution, like 100x100 for
more detail, the system would check and find that the resolution
saved to disk was 50x50. Thus, it returns "false", the file "cloth.dat"
must be parsed anew.
It would also return "false" if the file that should be loaded is
non-existant (due to deleting or such).

In this manner, it keeps track of the recently used variables and
would only reparse data if it can not be loaded with the
desired settings (defined by the vectors).

Am I still talking nonsense?

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde

>
>
> Tim Nikias wrote:
> >
> > [...]
> >
> > Now I've had the final idea: A set of macros designed to keep
> > track of the details being used, versus the former details, and
> > thus the need to generate anew or just load.
> > What the system would do was to attach an identifier (a string)
> > to a vector (5-component internally) and a filename (again, string).
> > You initialize the system, if possible, it loads and checks the old
> > data.
> > [...]
>
> Until here your writing was quite understandable but now you completely
> lost me - i have no idea what you are talking about.
>
> Christoph
>
> --
> POV-Ray tutorials, include files, Sim-POV,
> HCR-Edit and more: http://www.tu-bs.de/~y0013390/
> Last updated 31 Dec. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message