f1957dccb7
Having the on/off setting be backed by a boolean in dconf makes sense anyway but this is mainly to be able to remember the max accuracy set before user disabled geolocation so that when they enable it next time, we have the max accuracy level on same value as before. There hasn't been a real need for this but now we are about to add geolocation settings in control center and it'll be easiser for control-center to simply toggle a boolean property rather than to have to know about and deal with accuracy levels. Later we might also want to add accuracy level settings to privacy panel so keeping the accuracy level setting around still. However we no longer support 'off' accuracy level as the new boolean property covers that. This also implies that we no longer track available accuracy level, which made the code a bit hard to follow/maintain. https://bugzilla.gnome.org/show_bug.cgi?id=734483 |
||
|---|---|---|
| .. | ||
| accessibility.js | ||
| bluetooth.js | ||
| brightness.js | ||
| keyboard.js | ||
| location.js | ||
| network.js | ||
| power.js | ||
| rfkill.js | ||
| screencast.js | ||
| system.js | ||
| volume.js | ||