Length of paths is limited and I for example mostly do not save scene files. Could use this for rendered images of course, but then I prefer to name these by a sort of title appropriate to the image rather than by a list of the components used to make it. Could be stored in the exif data of the image files. Most image file formats have such facility.

I have been thinking more about a sort of metadata management system:

• adding a StartUpScript to a scene that will open a .py file that imports a PoserLogger module and defines the directory of loaded library items
• PoserLogger adding a callback function that will write that .py file when the scene is closed
• PoserLogger adding a callback function that will add any loaded library files to the list (Info is already in the Poser log file but that info cannot be assessed from Python and it does not give the path names)

I concluded there would be a few problems though:

• LoadLibrary Figure and its siblings do not even report if a load was successful, and the filename is not available unless I wrap scene.LoadLibraryFigure and find a way to ensure that my wrapper is called and not the original method.
• This list would hold all library files loaded during the development of the scene. It would not automatically be pruned.
• same holds for adding the metadata to the image files. Would have to wrap SaveImage()

Wrapping standard functions is a prescription for trouble of course. Guess this idea will have permanent residence in onedayland.