Report #3239
Toggling interface Booleans requires interface restart to apply
| source | Drakon Lameth |
|---|---|
| version | 0.1 |
| status | REJ |
| priority | TRI |
| target fix | |
| report date | 2024-02-03 19:16:57 |
| report | So, I decided I didn't like the compass being on screen, or the speedometer showing up when turning/moving around, so I consulted the Command Reference and discovered the @db toggle [boolean setting] command I proceeded to toggle off both compass and speedometer, but despite getting the "[16:53] Disabled interface.compass.enabled / [16:54] Disabled interface.speedometer.enabled " lines in chat for responses to the toggle, moving around (even turning in place) still caused the speedometer and compass to pop up on screen; it required use of @service interface restart, forcing the interface to restart itself, to take the changed values. If this is intended behavior, I'd suggest amending the "disabled" (or "enabled") responses to include a reminder to restart the interface service. If this is a bug, this is what this report's for then. |
9 months ago
rhet0rica:
This is definitely a misunderstanding of how settings in the database work. No part of ARES monitors the database for updates. The only settings change that takes effect (almost) immediately is id.callsign, and even that is only evaluated when the unit speaks. It is regrettable that the db command's message contributed to the confusion, but alas there's just not enough script memory for it to learn what settings go with what programs, as ARES has hundreds of config entries and dozens of database tables (and db is basically out of memory already).
Since you were reading the command reference page about interface, I'll make sure it firmly states the necessity of restarting the service.