A few ideas in case they are helpful:
Some applications put words on the canvas near the changed setting that say something like "Changes take effect after restart. Restart Now" (Firefox, for example, in the extension config) .
In other applications, if the situation merits more emphasis because the user should really do it now, a button appears [Restart (icon: arrow in a circle pointing counter clockwise or a reload icon with two arrows in a circle: 🔄)]. Likely there is already an icon designated for this in the icon set for the platform. Icons work best when they also have a textual label.
If you go with a dialog, I would put the button there so the user has something useful to do about it when notified. If restarting is optional, add a "Later" button too (or something similar) and give people another chance at the same dialog after another config choice or after some time has passed.
If the GUI config screen has all the options on one page, then you could show a pulsing restart button to remind people they have to do that when they are done, and then you might not need a separate dialog, especially if you write the message on the background canvas. If the page scrolls, this could mean putting the restart button top and bottom in order to be visible enough.
Susan
On May 16, 2016, at 7:58 AM, segfault <segfault@???> wrote:
> segfault:
>
> Now with your proposal B, we would have to apply the options when the
> on/off switch is clicked. But since there are other ways to start the
> service, for example via the CLI, this could lead to an incorrect state
> in the GUI, where the options don't display their correct state.
> This might be a bit far-fetched and maybe the user can't expect the GUI
> to be in a consistent state if he mixes it's use with the CLI - but this
> issue would not exist with the configuration dialog.
> _______________________________________________
> Tails-ux mailing list
> Tails-ux@???
> https://mailman.boum.org/listinfo/tails-ux
>
>
