I came up with one idea for saving files with Evaldraw when I was attempting a work around.
I thought I could take advantage of F6 to save a printf string containing the characters to represent data values when read. Of course it turns out F6 is not available in runonly mode.
However when it prompted me for a file name, I thought this would be a decent way of providing file saving without the risk of runway file and data creation.
Basicly allow printf exportation to file while running and file window prompt for giving the files a name.
I admit I haven't quite tested this out yet, creating a text file(actually a KC) using characters as data values and reading it back in evaldraw, creating potential save and highscore files for games.
So how well would allowing the F6 linked commands to be usable in runonly mode work? Either limiting them in some way or having a command that does the same function.
Awesoken at
Re: Possible saving method for Evaldraw
In the next release of Evaldraw: * Capture to file (must use F6 hotkey) now works in /runonly mode and uses .TXT as default file extension. * Add fprintf() and fputc(). These are now the only functions that write to the capture file. printf() and printchar() are no longer captured when the "capture to file" function is activated. This allows text to be displayed without it going to the capture file.