feat: Add config reload delay option and refactor reload logic

[ammen99]

Fixes #2493 and potentially other long standing issues related to config reload.

An open question is whether we want to set the default to something like 50 or leave it to 0 to keep the old behavior. Thoughts?

[soreau]

An open question is whether we want to set the default to something like 50 or leave it to 0 to keep the old behavior. Thoughts?

My opinion is that we should keep old behavior here and set the default to 0. For example with wcm, anything other than 0 would break i.e. scrolling on a spinner to change an int or float value and see the result in real-time.

The thing I would like to see fixed in all this is, starting wayfire with something like wayfire -c /tmp/wayfire.ini where /tmp/wayfire.ini does not exist, then while wayfire is running, creating that config file and changing it would work without having to restart wayfire.

[ammen99]

An open question is whether we want to set the default to something like 50 or leave it to 0 to keep the old behavior. Thoughts?

My opinion is that we should keep old behavior here and set the default to 0. For example with wcm, anything other than 0 would break i.e. scrolling on a spinner to change an int or float value and see the result in real-time.

The thing I would like to see fixed in all this is, starting wayfire with something like wayfire -c /tmp/wayfire.ini where /tmp/wayfire.ini does not exist, then while wayfire is running, creating that config file and changing it would work without having to restart wayfire.

Did we not fix this a long time ago? There is code for it in the default config backend at least.

[ammen99]

My opinion is that we should keep old behavior here and set the default to 0. For example with wcm, anything other than 0 would break i.e. scrolling on a spinner to change an int or float value and see the result in real-time.

Good point, I will set it to 0 by default.

[soreau]

The thing I would like to see fixed in all this is, starting wayfire with something like wayfire -c /tmp/wayfire.ini where /tmp/wayfire.ini does not exist, then while wayfire is running, creating that config file and changing it would work without having to restart wayfire.

Did we not fix this a long time ago? There is code for it in the default config backend at least.

Hm, I'm not sure if it works or not, would have to test it.

[killown]

Fixes #2493 and potentially other long standing issues related to config reload.

An open question is whether we want to set the default to something like 50 or leave it to 0 to keep the old behavior. Thoughts?

you pr is amazing, fixed the issue!

[killown]

WCM is working with 50ms.

This PR doesn't just fix the IPC issue, it also fix the outputs being disabled due to the config reload issue. This no longer happens.

I believe 50ms should be the default option, as it will prevent many issues, this pr is bigger than you imagine, besides the simple code.