Ok, couple of thoughts...

First off, it's your baby, so feel free to work on whatever floats your boat :).  I'm still pretty busy with freelance work, so I'll help when I can, but for the time-being, I just don't have any free time.  It just happens that some of the work I have could benefit from this script, if/when it could do more than one morph at a time and secondly, across multiple actors.

So having said that, my idea of multiple morphs, with only having to select source and target figures, an actor on each and multiple morphs is... well, that :).  As far as I know, this would only require allowing multiple selections on the morph list/column/scroller thingie, and then calling transfer_morph() repeatedly, with a new morph name each time (with the same source and target actors).

Currently, you can only transfer one morph.  After that, all the GUI lists are cleared and you have to select the source figure, select the target figure, select the source actor (which may require scrolling down the list first), select the target actor (which may require scrolling down the other list), selecting the morph (which may require scrolling THAT list) and clicking GO again.  When you multiply that times a couple dozen morphs... tedium sets in fast .

So, just to clarify - I'm talking about multiple different morphs.  Smile, Nose Big, Cheeks Poofy, in one go.

Next, the other part of that is handling multi-actor correlations.  This is a separate, but potentially related issue.  The best way to handle multi-actor correlations is probably by allowing multiple source actors to be selected, but only one target actor.  Correlations are then run between that target actor and the list of source actors.

If (or as long as) it's still all in one script and the user has selected multiple morphs, then those morphs are relative to source actor with the same name as the target actor selected.  Ideally, when just transfering morphs, they'd only need to select one actor on each.... the (pre-generated) data file would let the script know that it needed to load other cross-actor correlation files to satisfy all vertices of this target.

So the interface really only needs to change to allow multiple morphs to be selected, and once multi-actor correlation code is in place, multiple source actors.  The only thing complicating things is that fact that it's still all one script and you have code that does the correlation if the file(s) can't be found.  If it was two scripts, the morph transfer one would just throw up it's hands and tell the silly user to go run the correlation script first.  And the correlation script wouldn't care about morphs at all (oh, the tangled web we weave... :)).

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.