Azure Pipelines have been made to work well enough for this project. All other CI systems are to be disabled as mentioned dunder #308
Delete the .travis.yml file now that it is not longer needed. It can be recovered from git history if we ever wish to resurrect it.
A separate action will need to be taken by someone with administrator access to the present https://travis-ci.org/debauchee/barrier project to unlink from the system there.
We plan to remove all the CI pipeline apart from Microsoft Azue Pipelines. This was documented under #308 after the Azure Pipeline system was successfully integrated under #303 and shown to provide all the build targetes we needed.
As there are presently have 4 seperate main build targes. As well as giving the overall master branch status in the Readme (which forms part of the main page on github.com) also show the seperate build status. This makes it clear if a single part fails and gives an obvious indicator that this project works for Linux, Mac and Windows.
This commit adds suppotr for generating a 'compile commands' JSON
file. This provides fairly sufficient autocomplete support for most text
editors, such as (Neo)vim and VS Code. It specifies include paths, and
the compiler arguments used to compile each source file.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
The "Apply" button in the main window calls stopBarrier() immediately
followed by startBarrier(). The startBarrier() function reloads the
configuration. The fact that the "Apply" button applies configuration
changes is incidental; the "Start" button also applies new settings.
"Reload" more accurately describes the function that the button
performs.
Issue #284
Unlike other settings, the "Enable Clipboard Sharing" setting of the
ServerConfigDialog does not persist when the barrier application (GUI)
is stopped completely and restarted. Add the necessary code to the
saveSettings() and loadSettings() functions.
