I don't have the source code for the qconvex.exe.  I don't think they had the code available at their site (which is linked in the thread).  If you're asking because you're interested in how they build the hull, I do have a link somewhere to a (slightly buggy) Blender script which does the same thing, using Python in Blender.  If you want to know how qconvex receives and processes the data, I can't really help with that.  :(

Let's see.  We wouldn't be able to send Numeric arrays across to an external .exe.  The arguments would go across as strings.  What sort of format would a C application require for the information?  It would have to do some processing on its end, I think, to convert the arguments back into a form it can use.  I have code that can literally export the lists or arrays to a .txt file.  I think there's a basic function for that in the UV code for TDMT.

Ideally, I'd like to see our math library and these two alternate point-in-tri functions ported to an external app too, if that would speed things up.  That was to be my first test, porting the alternate point-tri stuff to see how speed is affected (because it would be easier for me to test all of this using the less complex shrink-wrapping script I'm working on right now than to alter TDMT).  But... one thing at a time, right?

So, how could we get the data across as strings, both ways?  What would need to happen on the C end to read things back in?  What sort of export formatting for the strings would be desirable, from Poser?

===========================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.