The was a problem with the original patch because it meant script writers could create scripts using clearRoomUserData() with the additional argument (the key for the data item to delete) and an un- patched Mudlet instance would delete ALL the user data for that room instead of just the unwanted item. Ah, the requirement to maintain backwards compatibility can bite you if you aren't careful! I'll see if I can combine the original patch with a fix-up and post it back here for reference.
-- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1275255 Title: Unable to examine/modify room UserData without knowing key Status in Mudlet the MUD client: New Bug description: The current LUA interface to the user room data is very limited. Knowledge of the key is required to use getRoomUserData(). Also, it is not possible to remove a specific key-value tuple from the user data even if one does know the key to use - a workaround to use the existing clearRoomUserData() to delete ALL the data and reinsert the remaining wanted items is unsafe because it is not possible currently to find out what the other items are! I attach a patch, a commit to MY current (master) repository at https://github.com/SlySven/Mudlet2 which addresses these issues. Due to differences this will not patch cleanly to the current master because of other changes in the same area of the TLuaInterpreter.h file but it should be possible to apply the modifications to most recent builds. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1275255/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
