New Functions for using Linkset Data with Tables
closed
SuzannaLinn Resident
table ll.LinksetDataListTable(start, count, pass?)
and table ll.LinksetDataFindTable(start, count, pass?)
- like llLinksetDataListKeysandllLinksetDataFindKeys, but returning a table with keys and values
- with optional parameter passfor protected values
table ll.LinksetDataWriteTable(table, pass?)
- returning a table with keys and errorcodes for the pairs not writen, an empty table means all ok
table ll.LinksetDataReadTable(pass?)
- returning all the linkset data
Log In
H
Harold Linden
marked this post as
closed
We're not looking to do many API changes in the leadup to general availability, but linkset data is definitely going to be revisited to give it a more Lua-ish API :)
Anna Salyx
for the last two, I am already doing this, basically, with
ll.LinksetDataWrite("mytable", lljson.encode(some_table))
and
local some_table = lljson.decode(ll.LinksetDataRead("mytable"))
Granted I'm doing it with very simple tables at the moment.
These new functions/methods would just streamline that by taking the middleman out of the process flow and, I presume, make it a bit more stable in terms of how data is translates from "exotic" values like vectors to and from the plain text that LSD utilizes? Yes?
I'm all for it for both reasons if that's the case.