aboutsummaryrefslogtreecommitdiff
path: root/src/app
diff options
context:
space:
mode:
author0neGal <mail@0negal.com>2022-02-24 00:25:15 +0100
committer0neGal <mail@0negal.com>2022-02-24 00:25:15 +0100
commit2c74233c21c27c45c79edb843cd5078a950b9ff6 (patch)
treea539e079d2e2ad6e58a0b8b9379ae1a03355c014 /src/app
parent5193485b5c66170330b920d891e3fe1442cc1f3d (diff)
downloadViper-2c74233c21c27c45c79edb843cd5078a950b9ff6.tar.gz
Viper-2c74233c21c27c45c79edb843cd5078a950b9ff6.zip
fixed NS never being auto-updated and more
When #87 was merged an unnoticed problem slipped in where if Viper was running in a version that did not support auto-updates we would never auto-update Northstar. Now that's fixed, and the nsupdate option is completely implemented. I also took the liberty of removing the auto-update option in the settings page if Viper can't auto-update anyway, as it's useless if that's not possible.
Diffstat (limited to 'src/app')
-rw-r--r--src/app/settings.js5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/app/settings.js b/src/app/settings.js
index 4921e07..902e57b 100644
--- a/src/app/settings.js
+++ b/src/app/settings.js
@@ -96,6 +96,11 @@ var Settings = {
}
}
}
+
+ ipcRenderer.send("can-autoupdate");
+ ipcRenderer.on("cant-autoupdate", () => {
+ document.querySelector(".option[name=autoupdate]").style.display = "none";
+ })
}
}