Communicate to users that the BlueMap process needs to be restarted when a config option is changed #102
Description
Whenever the config is changed, the BlueMap process needs to be restarted, so it reads the new configs.
Currently, this is not communicated anywhere, yet.
I'm not sure what the best way to do this is.
-
A message (toast/snackbar/popup/whatever) could be shown whenever the user changes a config option while the process is running, but I feel like that gets annoying.
-
It could also be written in the UI somewhere, but no-one will read that. And where should it even go where it does not look out of place?
-
Maybe the process should automatically restart whenever the user changes a config option? But that gets too "DDoS-ey".
- Or the process gets automatically restarted when the user goes back to the Control Panel. (If any config option was changed)
- Or a popup asking the user if it should restart.
-
The configs in the sidebar could be greyed out while the process is running, with a tooltip saying that the process should be stopped before they're unlocked again. But that feels too restrictive.
- Or the tabs could remain clickable, but the config options themselves could be greyed out while the process is running. But that would add a lot of code complexity, and I'm not sure how pleasant that would be either.
If anyone has any ideas, please comment!