Age | Commit message (Collapse) | Author |
|
|
|
* enhancement: update version printing format
as mentioned in #253, version numbers can be confusing if you don't know
or realize you're running SwayFX instead of standard sway.
to fix this issue, I've updated the way we display versions, replacing
"sway version X" to "swayfx version X", suffixed by the sway upstream
version which swayfx is based upon.
while not immediately displaying we come from swayfx in
swaymsg/swaynag/swaybar, we do display we're based off a specific
upstream sway version.
note: this requires updating `meson.build` (currently `meson.build:181`)
each time we rebase into a new sway version.
Closes: Issue #253
Signed-off-by: Mazunki Hoksaas <[email protected]>
* reduce linelength
---------
Signed-off-by: Mazunki Hoksaas <[email protected]>
|
|
* Create INSTALL-deb
* Rename INSTALL-deb to INSTALL-deb.md
* Update README.md to include debian
* Added a guide
* Update README.md
* Update INSTALL-deb.md
* Version change
|
|
|
|
|
|
|
|
* Increased blur size to match what WayFire uses
* Fix damage compensation not being scaled
|
|
|
|
One example would be the tiling indicator sometimes experiencing a "sharp" edge when the radii was larger than the
height/width
|
|
|
|
Simple fix in README.
|
|
* Added sway-portals.conf to AUR publish Action
* Bumped PKGBUILD pkgrel
|
|
Integrates commits c85a455e and 2f9c63b0 from extra/sway.
Copied from c85a455e:
> As of version 1.17, xdg-desktop-portal requires desktops to declare
> which portals should be used. For Sway, this requires a file
> /usr/share/xdg-desktop-portal/sway-portals.conf (or a local user
> config).
>
> A reasonable default is to use GTK for the file picker (as wlr doesn't
> have file picker support) and wlr for screencast/screenshot support.
> Fedora does this similarly. [1]
>
> Upstream is not interested in shipping a configuration file [2] so we
> need to do it downstream.
>
> [1] https://src.fedoraproject.org/rpms/sway/blob/rawhide/f/sway-portals.conf
> [2] https://github.com/swaywm/sway/issues/7773
https://gitlab.archlinux.org/archlinux/packaging/packages/sway/-/commit/c85a455eb653256b57b0b1661e398a48946e85b4
https://gitlab.archlinux.org/archlinux/packaging/packages/sway/-/commit/2f9c63b0539119acb63d6028c61d41c7faa1cebb
|
|
Update pkgrel twice for changes in #237 and #240
|
|
> swayfx/meson.build:92:2: ERROR: Assert failed: sd-bus-provider must
not be set to auto since auto_features != auto
|
|
|
|
|
|
|
|
* refactor: removed surface_width + surface_height from render_blur()
* Fixed scaling issues
* Minor refactors
* removed scaled_dst box
* removed uneeded fb bind
* removed unneeded src_box
* removed unneeded wlr_fbox_from_box function
* removed src_box
* Don't scale the blur translucent region twice
* Renamed extended_damage to original_damage to reflect better what it actually is
* Removed unneeded clearing of the wlr fbo before rendering onto it
* Removed the need for our own main FBO, also fixes some damage bugs
* Simplified detection of blur on workspace
* cleaned up comments
---------
Co-authored-by: Erik Reider <[email protected]>
|
|
|
|
|
|
|
|
* add updated mascot art
* Delete swayfx_mascot.png
* re-add old mascot image
oops
|
|
Co-authored-by: sntx <[email protected]>
|
|
|
|
|
|
* README: Inline the repology badge and swayfx mascot
* README: Removed unused style from html tag
|
|
|
|
* added check for smart
* expose gaps_to_edge
* add smart variable
|
|
|
|
|
|
|
|
The blur rendering logic includes the optimization to render blur only
for transparent surfaces. This patch considers surfaces as transparent
also when the transparency is only introduced by the dim color.
We can now have windows, that are opaque by default become transparent
with blurred background as soon as they loose focus.
Example configuration:
```
blur on
blur_passes 3
blur_radius 5
default_dim_inactive 0.15
dim_inactive_colors.unfocused #00000000
```
|
|
when `scratchpad_minimize` enabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This was backported to SwayFX in 3c2e38b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Will McKinnon <[email protected]>
|