Okay.  I need some feedback before I proceed with multiple morph transfers.  We need some information before we start.  We need source actors, target actors, and morph names.  The most complex way of doing this would require a lot of user-specification of correlations to use and morphs to use, and would require either massive re-design (and complication) of the GUI or a series of popups throughout the process to allow user-specification at each step.  Either way, that seems less a convenience for the user (and the programmer) than a hassle and a complication.

To automate this, we need to make some assumptions.  I would say we should walk the figure-figure correlation folder path, checking each actor-actor subfolder for a "full.vwt" datafile, then transferring the morph using that for each correlation set, IF the selected morph exists in that specific actor.  This requires at least two things: a proper TDMT folder path for the actors, and a "full.vwt" for them.  Presumably this is driven by one single morph selection for each run.  If not, we need a device to select multiple morphs.  

So making this GUI-driven is not easy or, presumably, accessible to the user.  To add these selection capabilities to the core GUI would make the other functions confusing to set up on the user-level.  But automating it is less flexible and rather restrictive.

So I need some input before I proceed.  What do you have in mind for this?  What parameters would you accept, or prefer?  Do you want to have to stop mid-process to keep making new selections, or do you want to press a button and have it go?  Do you want to handle one morph at a time, or several morphs?  We need to discuss this, I think.  And this may lead back tothe questions about datafile and datapath design and handling.

Whaddaya think?

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.