God saves the conf!
I think the problem is related to the fact that recently I have changed the minimum/max value types from integer to float, but I haven't considered any potential impact on import/export functionality.
I'm going to check it.
Oh and usually I do try to make the changes in a way that it doesn't brake previous setup
Unplug the fuse??? Are you kidding if you are to unplug all the fuse you can find in a typical British home one day won't be enough you have a fuse in every appliances cable, you have a fuse in every socket, you have a some more fuse in the fuse box, than you have the main fuse..... And if you are lucky some more hidden ))
Updated beta version, changelog:
- Fix for min/max values being ignored by the import/export
- Added French translation thanks to @fbike for the very quick turn-around and for providing it!
Some notes, the JSON file CAN include line breaks as well in case you want to edit it manually also order of the elements can be altered in the JSON in case you want to make it more humanly readable, the format of the JSON is a 2d array. Each setting is exported as an array with the following 3 fields:
- Field name
- Field value
- Type of field (S=String, I=Integer, B=Boolean, F=Float)
Therefore this is how each setting will look in the JSON:
Each gauge has the following settings (where X is the gauge number):
Beside this there are all other general settings (TPMS, Speed camera, etc) but they follow the same rule/structure
Hope this helps in case you want/need to manually edit the JSON files.
|android auto, androidauto, obd2, torque pro|
|Thread Tools||Search this Thread|