Seeing Cage's brilliant scripts for vertex-level editing made me think about the following: what if the boxes generated could be made to track the vertex they were created from, and then be used to parent objects to? For example, a nose ring that stays in place even when the face is morphed. Or a spike attached to a chin that stays put when the mouth is opened. The script would need to create two boxes: one for the vertex, and another placed at a user-defined distance from the first, along the vertex's normal (for point-at purposes). My idea for how to generate the boxes is as follows: the user selects several faces surrounding a single vertex, using the grouping tool. This would make it easier to precisely choose which vertex gets used.

I think this idea has something :)

Probably the idea should be reworded to come to an easier solution.
"The possibility to parent a prop to a group of polygons of a certain actor".

I changed to a polygon group because such a group can easily be handled with Posers Group Editor and selected polygon groups are rechable via Poser Python.

One method of resolution:

*If a prop is parented to an actor and group-parented to a predefined group,  the (computed) centerpoint coordinates from the selected polygongroup are saved as a reference point.

On each WorldspaceCallback the actual parentgroups centerpoint is computed. The child prop is moved by group_saved_startingpoint - group_actual_position (if they differ) and group_actual_position is saved as the new group_saved_startingpoint (all local coordinates, because the prop is also parented to the actor).

*"what if the boxes generated could be made to track the vertex they were created from, and then be used to parent objects to?"

*I think Ockham did something like this in his pseudo-parenting script, whatever it's called, although he perhaps didn't take the idea as far as what you're suggesting.  Unless I'm getting confused again, I think he uses worldvertex postions as the point of reference when applying the parenting in his script.

Thanks for the compliment.  :-P  Now I'll get a swelled head, and mess up (I mean mess up even more).  If you look at the quality of my code, however, it should be clear that my scripts aren't brilliant.  I keep hoping that some of the more capable and talented people around here will look at some of the potential that's been overlooked in PoserPython.  The Blender community has some real geniuses who constantly write free scripted utilities, Ideasman being my personal hero among them.  The Poser community is similarly dedicated to sharing, but fewer people seem to jump in and try to expand PoserPython.  Alas.  Maybe it's because Poser has become more marketplace driven....