Bug fixes for LinkSet Data related to matching SL behavior #68
Conversation
…o all scripts in all prims. Similar to attach which is currently handled here. Clean up some of the special case handling in LinksetData Write. Writing a key with no value is translated to a delete. We weren't handling that case. Also returned key value on a write, we were previously returning a null string.
…perate LinkssetData class. The SOP is one of those things thats already WAY to complex so hopefully this should make maintenance easier. Added code to merge LinksetData stores in order to handle linking 2 SOGs that both have LinksetData. Adjusted serialization handling so the database still stores just the KVPs and the wrapper class is constructed from that. Keeps it compatible with current saved data.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…hared entries. Still need to address shift-copy issues.
…opy. We use that when doing a copy of prims because otherwise the dictionary ends being referenced from both prims on a shift copy, etc. Also used on a merge to create new entries. Fixed some of the accounting code which was incorrectly reporting usage and terminating a copy early on a merge.
|
Liam Hoffen — Today at 11:40 AM |
Make the events posted for linkset_data go to all scripts in all prims. Similar to attach which is currently handled here. This is yengine only for the moment. XEngine doesn't seem to replicate the all-prims behavior for attach.
Clean up some of the special case handling in LinksetData Write. Writing a key with no value is translated to a delete. We weren't handling that case. Also returned key and value via the script event on a write, we were previously returning a null string for value.