## Description
#793
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the appropriate box . -->
- [x] Bugfix (Change which fixes an issue)
- [ ] New feature (Change which adds new functionality)
- [ ] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Fixed …
- Added …
## Testing
- [x] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
### How to test the changes
<!-- Optional, it can speed up review process if you provide the
information on how to test your changes. -->
No information provided.
## Description
Changes the [Switches](https://docs.gtk.org/gtk4/class.Switch.html) to
use the `active` property, which controls both color and position,
instead of `state`, which only changes the switch color.
It also sets the `activatable-widget` on the jsdeliver ActionRows
allowing the user to click anywhere to activate the switch.
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the box that apply. -->
- [ ] Bugfix (Change which fixes a issue)
- [ ] New feature (Change which adds new functionality)
- [x] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Fixed a bug where Switches were not shown as active
## Testing
- [x] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
### How to test the changes
<!-- Optional, it can speed up review process if you provide the
information on how to test your changes. -->
1. Open the preferences
2. Notice how the switches have both the correct position and color
@FineFindus
## Description
Changes the `text-value-toggle` tooltip-text to either display `Show
Hex` or `Show Color` depending on which child is currently visible.
Depends on https://github.com/GradienceTeam/Gradience/pull/789
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the box that apply. -->
- [ ] Bugfix (Change which fixes a issue)
- [x] New feature (Change which adds new functionality)
- [ ] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Improved tooltip for toggling color values
## Testing
- [x] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
### How to test the changes
<!-- Optional, it can speed up review process if you provide the
information on how to test your changes. -->
1. Open the app
2. View tooltip of the `text-value-toggle` button
3. Click the `text-value-toggle ` button
4. Notice how the tooltip changes
## Description
Sets the `activatable-widget` on ActionRows, allowing the user to click
the row itself to activate the child widget. This brings it more inline
with the default libadwaita ActionRows, e.g. ComboRow. It is only done
for non-destructible actions.
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the box that apply. -->
- [x] Bugfix (Change which fixes a issue)
- [ ] New feature (Change which adds new functionality)
- [ ] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Fixed clicking on rows to activate their children
## Testing
- [x] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
### How to test the changes
<!-- Optional, it can speed up review process if you provide the
information on how to test your changes. -->
1. Open the app
2. Click on an ActionRow, e.g. an OptionRow
3. Notice how the ColorDialog is opened
## Description
Fixes various typos and improves the wording in the
[pr-template](f2ae26c281/.github/pull_request_template.md).
Fixes #(issue) <!-- Remove this, if your PR doesn't fix any tracked
issue. -->
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the box that apply. -->
- [x] Bugfix (Change which fixes a issue)
- [ ] New feature (Change which adds new functionality)
- [ ] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Fixed typos in the pr template
## Testing
- [x] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
## Description
<!-- Describe your changes in detail here. -->
Fixes #(issue) <!-- Remove this, if your PR doesn't fix any tracked
issue. -->
## Type of change
<!-- What type of change does your pull request introduce? Put an `x` in
the box that apply. -->
- [ ] Bugfix (Change which fixes a issue)
- [ ] New feature (Change which adds new functionality)
- [ ] Enhancement (Change which slightly improves existing code)
- [ ] Breaking change (This change will introduce incompatibility with
existing functionality)
## Changelog <!-- This is optional, but highly appreciated. -->
- Fixed …
- Added …
## Testing
- [ ] I have tested my changes and verified that they work as expected
<!-- Make sure you did this step before marking your PR as ready for
merge. -->
### How to test the changes
<!-- Optional, it can speed up review process if you provide the
information on how to test your changes. -->
No information provided.
