diff options
author | 0neGal <mail@0negal.com> | 2022-04-17 16:34:41 +0200 |
---|---|---|
committer | 0neGal <mail@0negal.com> | 2022-04-17 16:37:33 +0200 |
commit | b4226cf152fa4ac35f7fe19a06a307ad026068c7 (patch) | |
tree | 35c80ace03c3b29ddc6951f08e4c2130801df749 /src/app/settings.js | |
parent | 1438d0634fad9129a3edb943f007da3dadedf834 (diff) | |
download | Viper-b4226cf152fa4ac35f7fe19a06a307ad026068c7.tar.gz Viper-b4226cf152fa4ac35f7fe19a06a307ad026068c7.zip |
changing the language now disables autolang
This is for the sake of UX, as a user might be confused about why it
doesn't work as they may not notice that they've to turn off auto-detect
language first.
Because of this Settings.switch() now has a state value, and if you
provide a DOM element as the element arg it now uses that to know what
to toggle, before we used to just provide a number, which made sense for
generating the onclick events, but not for this task...
This whole thing was brought up because of #115
Diffstat (limited to 'src/app/settings.js')
-rw-r--r-- | src/app/settings.js | 20 |
1 files changed, 15 insertions, 5 deletions
diff --git a/src/app/settings.js b/src/app/settings.js index 853cd0b..23b38c9 100644 --- a/src/app/settings.js +++ b/src/app/settings.js @@ -31,16 +31,26 @@ var Settings = { switches[i].setAttribute("onclick", `Settings.switch(${i})`); } }, - switch: (element) => { + switch: (element, state) => { let switches = document.querySelectorAll(".switch"); - element = switches[element]; + if (switches[element]) { + element = switches[element]; + } + + let on = () => { + element.classList.add("on"); + element.classList.remove("off"); + } - if (element.classList.contains("on")) { + let off = () => { element.classList.add("off"); element.classList.remove("on"); + } + + if (state != undefined) { + if (state) {on()} else {off()} } else { - element.classList.add("on"); - element.classList.remove("off"); + if (element.classList.contains("on")) {off()} else {on()} } Settings.reloadSwitches(); |