Those are good ideas. You've got me thinking. I'll have to do something slightly different to that first method because valueParms are often slaves of other valueParms. Can we access what's stored in a parameter's memorised setting? (what you get when you do a "memorise figure" then read from for a "restore figure"). I'm thinking I could read from those and store, overwrite them with a memorise figure method if there is one, read from the new values to write the pose, then set the memorised values back how they were. While I can see that having Value report effective values rather than visible setting for some things would be useful under some circumstances, I can imagine this isn't the only time where it gets in the way. For a start, Value and SetValue aren't doing the same thing. SetValue sets the actual dial setting while Value reads the effective dial setting. If you tried a script meant to reset dials based on their current setting, you'd be screwed. For example, a sript that's meant to halve parameter settings would look at a dial set to 1 with a master set to 20 (slave's effecive value = 21) and would then reset the slave to 10.5 instead of 0.5 while correctly setting the master to 10, giving you an effective value of 20.5 in the slave instead of the desired effective value of 10.5. That sort of thing could give you some real screw ups. I reckon they need two methods - one to read the dial setting and one to read the effecive value of the parameter.

View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message