dfa1cb7ca5
Previously the editor and palette listened to Gtk.Settings notify::gtk-theme-name (and notify::gtk-application-prefer-dark-theme) to re-render their themed icons on theme switch. Two problems: 1. The initial icon load happened during widget construction, before the buttons were attached to the toolbar — so the style context resolved to a default (often white) foreground rather than the actual theme text color. Icons showed up white until the first theme-change event. 2. Settings notify fires *before* GTK's CSS engine re-resolves styles for the new theme. Reading the style context's foreground from that handler returned the previous theme's color, so toggling light <-> dark left both states settling on the same shade. Move both responsibilities into a new attach_themed_icon helper in _icons.py: it does the initial load, connects to the *button's own* style-updated signal, and rebuilds the icon on each emission. That signal fires *after* CSS resolution (both on first realize and on runtime theme switches), so the foreground we read is always the current one. A per-button color-key guard skips the rebuild when the resolved foreground hasn't changed, so unrelated style-updated emissions (hover, focus, active) don't trigger needless re-renders. The handler is connected to the button itself, so GTK cleans it up when the button is destroyed; both editor.py and palette.py drop their bespoke Gtk.Settings handler bookkeeping. |
||
|---|---|---|
| .github | ||
| bin | ||
| docs | ||
| lib | ||
| po | ||
| rules.d | ||
| rules.d-uinput | ||
| share | ||
| tests | ||
| tools | ||
| .coveragerc | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .python-version | ||
| CHANGELOG.md | ||
| COPYRIGHT | ||
| LICENSE.txt | ||
| MANIFEST.in | ||
| Makefile | ||
| README.md | ||
| RELEASE.md | ||
| RHEL.md | ||
| Release_Notes.md | ||
| mkdocs.yml | ||
| pyproject.toml | ||
| release.sh | ||
| setup.py | ||
README.md
Solaar
Solaar is a Linux manager for many Logitech keyboards, mice, and other devices that connect wirelessly to a Unifying, Bolt, Lightspeed or Nano receiver as well as many Logitech devices that connect via a USB cable or Bluetooth. Solaar is not a device driver and responds only to special messages from devices that are otherwise ignored by the Linux input system.
More Information - Usage - Capabilities - Rules - Manual Installation - Known Issues
Solaar supports:
- pairing/unpairing of devices with receivers
- configuring device settings
- custom button configuration
- running rules in response to special messages from devices
For more information see the main Solaar documentation page. -
Installation Packages
Up-to-date prebuilt packages are available for some Linux distros (e.g., Fedora) in their standard repositories. If a recent version of Solaar is not available from the standard repositories for your distribution, you can try one of these packages:
- Arch solaar package in the extra repository
- Ubuntu/Kubuntu package in Solaar stable ppa
- NixOS Flake package in Svenum/Solaar-Flake
Solaar is available from some other repositories but may be several versions behind the current version:
- a Debian package, courtesy of Stephen Kitt
- a Ubuntu package is available from universe repository
- a Gentoo package, courtesy of Carlos Silva and Tim Harder
- a Mageia package, courtesy of David Geiger