pattrstorage does not store all client object data in all slots

Jan 2, 2010 at 6:29am

pattrstorage does not store all client object data in all slots

I hope can explain this well enough to get some help. I am using multiple autopattrs in multiple sub-patches, and all works well. My problem is that if I don’t change a client object value then it doesn’t get stored in that preset slot. I have tried various combinations of outputmode and changemode, but I can’t get object values that have never been changed to store a value.

This means that as I move through slots that do have stored values and then move to a slot that does not, the value of the previous slot is imposed on the valueless slot. Going through and manipulating every value that is not stored to trigger the patterstorage to store is very undesirable, but I see no other way. What am I missing?

#47521
Jan 6, 2010 at 12:04pm

Please submit a patch so that we can test this. Thanks!

Jeremy

#170955

You must be logged in to reply to this topic.