You have to wrap the value in quotes so that it will be treated as a string rather than a float. It is not possible any other way as a comma is used as the delimiter between objects and values (whitespace is ignored).

That is already supported kind of. You just need to use Set /file with a node path to load a JSON file into. The only thing you cannot do is serialize a specific node to a file, which is where a change would be necessary. How much do you need multiple instance support (give an example of usage)?

I'm using in-memory json to store lots of my own user-specific data rather than tons of global variables.
Then I want to open up a program's settings file which is also in json, add a value and resave that settings.json.

It's also useful to separate different blocks of data and only serialize the parts I need during debug.

I guess the only thing that's really needed is the ability to serialize a specific node.

Unless I can find a better solution for my in-memory storage... Actually, thinking about it I could probably use your arrays plugin and do arrays of pointers to arrays using a counter or concatenating names like
CarPark0 = array of license plates (e.g. 0=ABC123, 1=DEF456, 2=GHI789)
CarPark0_ABC123 = array of that particular car's properties (e.g. Make=ShinyThingsInc, Color=Green)

So yeah, it probably isn't necessary to have the json plugin handle more than 1 root json object at a time. I'll just write my own serializer for the arrays.

I could not reproduce this with the new build so it may be fixed. The full output string (66224 bytes) is correctly written to the output file for both the ANSI and Unicode versions. No memory access violations were caught in the debugger either.

1.0.1.2 - 12th July 2014
* Fixed crash on serialization to file for node values larger than 64KB.
* Fixed crash on serialization to stack for JSON larger than NSIS_MAX_STRLEN. The JSON will now be truncated.

The file serialization doesn't use any temporary buffer any more (it just writes directly to the file) so no reallocation was necessary.

Hi,
I am trying to use nsJSON plug-in and just find out that comment '//' does disturb somehow the parser, and break the reading of any node inside the file...
I'll temporally avoid using comment until I find a proper solution!
Cheers,
Pascal

Hey, Stu
The new Quote function doesn't escape strings whose first and last characters are already quotemarks. For example, nsjson::Quote `"some"text"`

The output is:

Quote:

"some\"text"

This is correct assuming the original feature request was to only surround the string in quotes if it isn't so already. Nevertheless:

Quote:

1.1.0.2 - 9th December 2015
* Get function /type switch returns an empty string if the node does not exist.
* Added /always switch to Quote function which surrounds the input string in quotes even if it is already quoted.