Recipe buffer + loadstring() core function

Case number:699969-994274
Opened by:Jean-Bob
Opened on:Wednesday, January 9, 2013 - 04:26
Last modified:Wednesday, January 9, 2013 - 19:26

Hi, I'm currently working on a save/load module for my recipes. The module stores the data I need on a note on seg #1, and I must use a custom func to fetch the data. Both workarounds are but ugly tinkering. So what I'm asking is: could we have some special buffer like a hidden seg #0 to store recipe data? The lua core function loadstring() could be a great tool too. As I don't get why we can't use this func, maybe extending the save namespace with some save.LoadObject() should get everyone happy(?).

Thanks in advance

(Wed, 01/09/2013 - 04:26  |  2 comments)

brow42's picture
User offline. Last seen 1 year 30 weeks ago. Offline
Joined: 09/19/2011
Groups: None

Persistent storage would be great...right now I consider using notes an abuse of the interface, and I'm sure that was one of the the things that drove selection interface users batty when selection interface had notes permanently enabled.

Tlaloc is the one who made the judgement calls for what made it into the Lua 2 API. You'll have to check with him, but a few comments about what might or might not appear in Lua 2 can be found at .

Joined: 08/24/2011

"right now I consider using notes an abuse of the interface" that's my point, and loadstring can be implemented as to avoid all threats.

The whole point of this suggestion is finding a way out of the deadend "pause script" thing. BetaHelix said the problem would be solved "in a few weeks"... a year ago. Responding to this suggestion would be just another workaround but way cleaner than how we can deal with this problem for now.


Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons