Perhaps I may not have mentioned it anywhere, but I have arranged it so that passing NULL as the item for the custom property to be attached to will cause it to become a 'global' custom property. I think if you try setting the property like this it should be saved correctly:
Ok, I will try passing a NULL from my SW to see if the code writes values to Json.
But I have several 'world' custom properties set in Rube which I would like to preserve in Json.
And with passing writeCustomPropertiesToJson(world) these values set in Rube get written to Json as well.
So is the intention that I have to write to Json the custom values from Rube in my software 'by hand' with
setCustomInt( NULL, "myint", 123 ); ?
I have tried passing a NULL to setCustomInt(), but then the code does not compile. The compiler complains about ambiguous function and the compiler can not decide which function to use.
If I pass a b2world pointer to setCustomInt(), and as explained above, pass a b2world pointer to writeCustomPropertiesToJson() everything works ok.
I guess I do not get how to use the functions.
As it works OK with the current code, shall I just leave it as it is ?