Hm, thats an idea...

But its not very platform-unspecific. Your system might end up with
filenames like "foo_243515_124512.dat" which would be too long
for some platforms.
On the other hand, your system makes it possible to keep older
files...
Perhaps I should keep track of several changes instead of the last
one? I'm not sure, but IMHO you mostly need only a max of 4
levels of details, these I could keep track of. The ending of the filename
would be referred by that...
Hm, I could even go as far as 1000 backtraces, using that idea for
the settings-saving-file itself...

I'll ponder a little more, suggestions?

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

> > In a seperate file, I'm saving all input settings, and then
> > compare these input settings to the ones formerly saved.
> > If they are the same, and if the file exists, it will just
> > be loaded.
>
> My idea was that instead of having second file with parameters, you can use
> filename to store settings. Whole version checking is made via file_exist().
> For example:
>
> #macro Make_Mesh(X_Grid,Y_Grid)
>   #local FileName = "my_mesh_" ;
>   #local FileName = concat( FileName , str( X_Grid , 0 , 0 ) );
>   #local FileName = concat( FileName , "_" );
>   #local FileName = concat( FileName , str( Y_Grid , 0 , 0 ) );
>   #local FileName = concat( FileName , ".mcr" );
>   #if(file_exist(FileName))
>     #include FileName
>   #else
>     #fopen MyFile FileName write
>     :
>     #write (MyFile,...)
>     :
>     #fclose MyFile
>   #end
> #end
>
> > This makes it possible to use the system for all kinds of
> > files, may it be meshes as pure vector-data, or the meshes
> > plus triangles themselves, or CSG etc etc.
>
> This makes it possible too :-)
>
> ABX

Post a reply to this message