To clarify some more:

That morph transfer process I've mentioned is actually part of a larger program that I use to transfer information between different versions of the mesh during development. I use .obj files as the lowest common denominator to get the data from one program to another, but even that doesn't always guarantee that I won't lose grouping information, vertex order, etc. So that transfer program has helped me enormously to stay sane during the development process.

One aspect of this is that the final grouping and the UV mapping were done in the high-poly version, whereas for pretty much everything else I tend to work with the low-poly one. So the need arose to somehow get that information transferred. That's why I don't care about other morph transfer programs. They just wouldn't help me with what I need to do. But I haven't really made that clear before, so I can't blame anyone for misunderstanding.

With that out of the way: easy morph transfer between different resolution versions of the figure would indeed be a neat side effect of what I have done. So my question was whether it might be worth it to translate some of my code into Poser Python so that a user could - for example - easily apply morphs to the figure that were  made for a different resolution than the one the user has currently loaded. Again, that wouldn't quite be the same as using an external program for transferring the morphs. For one thing, if one only needed the transferred morph once, there would be no need to save it to an extra file.

This is all a bit far-fetched at the moment, but the reason I'm asking now is this: if I end up translating my code into Python anyway, I might as well do it now while it's only a thousand lines long. But so far it seems like, although there is considerable interest in the lo-res figure, people would be quite happy to use external programs for transferring morphs. Which is fine by me, because it obviously saves me a lot of work.

-- I'm not mad at you, just Westphalian.