You'll have to excuse the obtuseness on my part - I've only just realized the main point of your suggestion...

adp001 posted at 11:57 AM Thu, 16 September 2021 - #4427549

...kValueOpTypeCodePYTHONCALLBACK is a regular Poser Python Parameter...

Just before I fell asleep last night a part of my brain that I'd been ignoring suddenly said "That's one of the valueOps that actually go in the CR2, like valueOpKey and valueOpTimes!". So this is a way to do it in the CR2 using valueOps... but with a tiny little bit of Python.

The only problem that I can can really foresee is that this won't work in DAZ Studio (that's one of the main reasons I didn't want to use Python - a Python solution would require me doing a DAZ Script version if I want it to work in DAZ Studio, and I lost interest in doing both Python and DAZ Script versions of things several years ago). So I think maybe I'll make this Poser only.

Thanks again adp001 :)

P.S. I've also just realized that the post editor has definitely changed very recently. It seems to be an improvement (finally scrapping Markdown!) but as you pointed out it's introduced different problems. Ho-hum.

---

The 3Dcheapskate* occasionally posts sensible stuff. Usually by accident.
And it usually uses Poser 11, with units set to inches. Except when it's using Poser 6 or PP2014, or when its units are set to PNU.

*also available in ShareCG, DAZ, and HiveWire3D flavours (the DeviantArt and CGBytes flavour have been discontinued).