From 69be5dbbc7ad7770ddca97a13edc4dd21d9d4ab1 Mon Sep 17 00:00:00 2001 From: Daniele Gobbetti Date: Sun, 26 Jun 2016 14:13:47 +0200 Subject: [PATCH] Set the json directly instead of using parseconfig Some watchfaces do some processing on the incoming json, and we are storing the json after the fact, and double parsing isn't good. --- .../main/assets/app_config/js/gadgetbridge_boilerplate.js | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/app/src/main/assets/app_config/js/gadgetbridge_boilerplate.js b/app/src/main/assets/app_config/js/gadgetbridge_boilerplate.js index 81cf1548..d3021c31 100644 --- a/app/src/main/assets/app_config/js/gadgetbridge_boilerplate.js +++ b/app/src/main/assets/app_config/js/gadgetbridge_boilerplate.js @@ -101,11 +101,8 @@ function gbPebble() { for (var i = 0; i < presetElements.length; i ++) { presetElements[i].style.display = 'none'; } - var json_string = GBjs.getAppStoredPreset(); - var t = new Object(); - t.response = json_string; - if (json_string != '') - Pebble.parseconfig(t); + self.configurationValues = GBjs.getAppStoredPreset(); + document.getElementById("jsondata").innerHTML=self.configurationValues; } //needs to be called like this because of original Pebble function name