There have been a few issues reported where remembering to restart the TouchCursor service after some changes to the config file are made was the cause of the issue.
Solution
Add a comment to the default config file reminding to restart the TouchCursor service after some changes to the config file are made to apply them.
Testing
This PR should not break anything as it just adds a single comment to the config file. Furthermore, all tests from test.c pass. I am using my version of TouchCursor with this PR included and everything has worked flawlessly so far.
Reason for this pull request
There have been a few issues reported where remembering to restart the TouchCursor service after some changes to the config file are made was the cause of the issue.
Solution
Add a comment to the default config file reminding to restart the TouchCursor service after some changes to the config file are made to apply them.
Testing
This PR should not break anything as it just adds a single comment to the config file. Furthermore, all tests from test.c pass. I am using my version of TouchCursor with this PR included and everything has worked flawlessly so far.