This change improves how the `create-macos-launchagent.sh` script locates the `solaar` executable.
Previously, the script defaulted to a hardcoded path (`/opt/homebrew/bin/solaar`) and would exit with an error if that specific file was not found and executable. This was too restrictive and failed in environments where `solaar` is installed in a different location, such as through `pipx` or in standard system paths like `/usr/local/bin`.
Now, the script defaults the `SOLAAR_PATH` to just `solaar` and uses the `command -v` utility to find the executable in the user's `PATH`. This allows the system to resolve the correct location of the `solaar` binary automatically. If the executable cannot be found in the `PATH`, the script now issues a warning instead of exiting, and proceeds to use the provided `SOLAAR_PATH` value in the generated LaunchAgent plist. This makes the script more flexible and robust for different installation methods.
The `create-macos-app.sh` script previously defaulted to a hardcoded Homebrew path for the `solaar` executable. This change removes the specific path, defaulting instead to `solaar`.
This modification makes the script more flexible and robust. It allows the system's `PATH` to resolve the location of the `solaar` binary, accommodating various installation methods beyond a fixed Homebrew directory. The explicit check for the executable's existence is also removed, as the script will now rely on the command being available in the shell's environment, which is a more standard approach.
This change introduces two new helper scripts for macOS users to improve integration with the operating system.
The `create-macos-app.sh` script builds a minimal `.app` wrapper for Solaar. This allows Solaar to be treated as a standard macOS application, enabling it to request necessary permissions, such as input monitoring, and to be discoverable by the OS. The script generates the required directory structure, a wrapper executable to launch Solaar, a standard `Info.plist` file, and an application icon from the source PNG.
The `create-macos-launchagent.sh` script sets up a LaunchAgent to automatically start Solaar at login and keep it running in the background. This ensures that the Solaar process is always available for device management without requiring manual intervention from the user. The script also configures log file locations for standard output and error streams.
Together, these scripts provide a more native and user-friendly experience for Solaar on macOS.
https://github.com/pwr-Solaar/Solaar/issues/1244
Set theme jekyll-theme-slate
update _config.yml
move some files around
add an index file
delete files that will no longer be needed
include jekyll front matter
Update the index page layout to use updated template
re-create the page layout from the updated template
add a favicon
remove manual gh pages build script
use master branch docs/ folder instead
add favicon to default layout
move layouts and includes back because of restriction with gh pages
testing: move index back into project root
move everything under docs, including config.yml
dont put the favicon in _includes
Fix building locally, fix logo
- resize the original logo document so that it doesn't have extra whitespace
- style the logo to match the original page
- fix issue when building locally, repo format was incorrect
Ignore files that are specific to documentation
add a readme that describes how to build the docs
remove downloads, since installation instructions are provided elsewhere
fix broken links in index page
fix the page header on all non-index pages
use site.baseurl for images
fix urls when on testing site with baseurl
Added another location to scan in function unfmt() due to fact that gtk30.mo and gtk30-properties.mo are found in /usr/share/locale-langpack/ instead of /usr/share/locale/.
00 is documented in HID++ 1.0 specification, it should be safe to set the 00
register. As another program may have written the notifications register
already and since enabling notifications has side-effects such as "disabling"
certaing functions, restore the flags after reading out available notifs.