> > On an unrelated side note. I have array parameters and associated java > > scripting happening at the moment. So I've got javascripts > accessing mesh > > vertices working, its really neat. > > Every piece that gets added makes the scripting more versitile. > Hopefully there is enough code in the scripting area that if someone > really wants to make a contribution they can see how to do it. Working > at the vertex level is a big plus for a programmatic interface. IIRC, > I'd only provided hooks to do manipulate vertices in a mesh through > function calls. Array manipulations are much more convenient for many > operations - perhaps a way to implement mesh modifiers. > I've put all my changes in a new branch in CVS, under the PARAM_INTERFACE_CHANGES branch. To do a checkout under this branch, go to the Checkout Options tab in WinCVS, and check the "By Revision/tag/branch" box, and type in PARAM_INTERFACE_CHANGES. It will check out that branch with all my changes. In this branch, I am also changing the .azt file reader/writer, so it is less prone to changes. The plan is to be a dual ASCII/binary file format with little effort to change between the two, and it uses the MParameterObject's to save and load data. This makes it much more resistant to changes in the Aztec code, where any minor change in the read/write methods in any class would break the whole thing. Also, the code used to save and load files will not be part of the object model, which was making things a real pain. It can't read in files right now, but it can save files. So if you feel up to it, check out the branch, and save a scene that has a variety of objects in it to get a feel for what it might look like. I achieve compatibility with previous versions, I intend on writing a plugin for each version of Aztec that will output to the new format, so old files can be read in. Phil