Updating of the electron also causes an update of the electron-settings package. The newer version of this package changed the default name of the settings file. To keep user settings we've changed the filename, but only in the main process. So it produced a bug when the user compile&upload something with third-party C++ libraries — the libraries from his workspace does not copy if he set a workspace in the custom (not default) path.
How it fixed?
On loading/saving settings we always set the path and file name for the settings file (for both kinds of processes).
There is no issue 😬
What was wrong?
Updating of the electron also causes an update of the
electron-settingspackage. The newer version of this package changed the default name of the settings file. To keep user settings we've changed the filename, but only in the main process. So it produced a bug when the user compile&upload something with third-party C++ libraries — the libraries from his workspace does not copy if he set a workspace in the custom (not default) path.How it fixed?
On loading/saving settings we always set the path and file name for the settings file (for both kinds of processes).