Dec 10 2012 | 9:56 pm
    I'm curious if anyone is making use of setstoredvalue, and is having good results. My own results are less than encouraging.
    Perhaps I've misunderstood things, but shouldn't setstoredvalue set the value of an object's stored value in the corresponding slot register? i.e. there should be no reason to then send pattrstorage a 'save' message to redundantly store the value that I set with setstoredvalue? Testing thus far seems to result in sporadic success, but nothing dependable.
    I'm curious if anyone is using this functionality and can vouch for it. I'll try to set up some simpler tests and post results if things aren't functioning correctly before going any further, but it would be useful to know what the expected behavior is: maybe I'm just assuming things.

    • Dec 11 2012 | 8:31 am
      I answered my own question. Everything works as it should (and as I assumed it did). Turns out I was calling setstoredvalue with a non-pattr object's name in some instances (I was using the scripting name of the linked object instead), and this is why I was getting seemingly inconsistent behavior.