Yann , thanks for checking, yes a couple of things
setting path and running thru current seems the most logical thing to do, if you know the correct way to do so, i dont think a root foreach would be that much use, setting the root outside the foreach loop is what i eventually did and works great.
is also made the mistake that when importing a json file i didn't make a root object, this somehow also screws things up, not sure if thats also in my capx example, but the structure looks fine a first sight (there's also a root object) but i think its not recognised as such.
as first time user, working with the json plugin (json for that matter), i found the 0 and 1 for value, the most confusing (at start) as you have the currentKey but not currentValue + the naming order, a path has to exist but a key doesn't, as in.. you set the key at a nonexistend name, you don't have to create it like an object (and this also creates a path) and an object you create and set
edit: if you return an arrayProperty in for each, the arrayposition is a string, that can be confusing..
as for path saving, i had the same idea, also if you could save the path, you probably are most likely to want to save a path to an array or object,
you could create a json path "folder" filled with arrays at firstrun, and name them "key" & "path" , but indeed if you don't know the structure, indicating what the path is, would be harder i guess, on the other side json is very fast so iterating thru the structure is already fast and some shortcuts can always been made
when im there, i will try those function out, i like the function.paramCount one