I’ll think about this, and appreciate the input.
There are a couple of problems that I see with this method. First, it will multiply the size of the libraries, possibly many, many times. The duplication of particle shape images (one copy for each emitter) can really add up to some big HD space. Right now, all of the free libraries total up to about 200 MB. Suppose that the new “folder for each emitter” (FFEE) approach results in a tripling of library size (which I think is a conservative estimate). That’s 600 MB, not including all of the overhead of over 1500 emitter folders, and image subfolders. Then add in library backups if you do any editing of libraries at all, and you’re talking a couple of GB of space. Maybe not a lot when you can get a 250GB HD for $100, but I think it’s still a lot.
The second issue is that using the FFEE method you now enable people to corrupt and change emitter libraries, and even emitters themselves from outside of particleIllusion. I really do not want to do that. Does it let the power user do some things that would be harder within pIllusion? Maybe. But the potential for problems far outweighs this in my opinion.
Keep thinking though. A redo of the library system is on the “to do” list.
FYI, Apple Motion keeps all particle images in a specific folder, and they are then accessed by all particle emitters, whether in library or in a project. There are advantages to this, and it may be the solution to the problems with your FFEE method. As I said, I’ll keep thinking.
Alan.
wondertouch