live-input-configuation

[AlanGriffiths]

Allow servers to dynamically update input configuration.

There's a very simple "mir_demo_server.input" addition to mir_demo_server to exercise part of this API, but that is not intended prototype.

[AlanGriffiths]

This is still not complete:

• There's no code/tests to exercise this API
• There's no facility to recover the default or configured configuration

[Saviq]

Recap of discussion:

• input configuration should remain in the main .config file
• we're leaning towards SIGHUP-reloading of the main config file
  • incrementally we'll enable live reinterpretation of the individual options
  • initial target are the input configuration options
  • some might not ever become re-interpretable
• as today, environment variables and command line takes precedence, basically making those static

[AlanGriffiths]

• input configuration should remain in the main .config file

I don't think that a (hypothetical) input configuration utility should be updating the main .config file

[Saviq]

I don't think that a (hypothetical) input configuration utility should be updating the main .config file

Agree, that will have to come from the shell implementation, e.g. integrating gsettings.

[AlanGriffiths]

I don't think that a (hypothetical) input configuration utility should be updating the main .config file

Agree, that will have to come from the shell implementation, e.g. integrating gsettings.

Right, so the input configuration needs to be exposed (like this WIP), not "remain in the main .config file"

[Saviq]

Right, so the input configuration needs to be exposed (like this WIP), not "remain in the main .config file"

Sorry, different trains of thought. …as opposed to a dedicated file.

[mattkae]

Some minor things, but seems like a good change overall! Now we just need to get the keyboard stuff in there too :)

[mattkae]

This appears to be a sensible change form the options that I tested!

[AlanGriffiths]

Seems I'm plagued with #3581 today