Skip to content

feat: Add vibrancy and configuration options#133

Open
veryard wants to merge 8 commits intoglzr-io:mainfrom
veryard:main
Open

feat: Add vibrancy and configuration options#133
veryard wants to merge 8 commits intoglzr-io:mainfrom
veryard:main

Conversation

@veryard
Copy link
Contributor

@veryard veryard commented Oct 27, 2024

This closes the following: #93

Notes:

  1. Color isn't widely supported, only Windows 10 v1903+, no effect on Windows 7 or Windows 11 (https://docs.rs/tauri-utils/latest/x86_64-apple-darwin/tauri_utils/config/struct.WindowEffectsConfig.html#structfield.color)
  2. Blur: bad performance when resizing - Should be fine considering zebar should pin to top (https://github.com/tauri-apps/window-vibrancy?tab=readme-ov-file#available-functions)
  3. Acrylic: bad performance when resizing - Should be fine considering zebar should pin to top (https://github.com/tauri-apps/window-vibrancy?tab=readme-ov-file#available-functions)

Testing:

  • MacOS: I do not have a Macbook so I left it out for now.
  • Windows 10: Will boot up a VM this coming week to verify, unless someone can give it a crack for me.

New configuration options:

  • backgroundEffect: None, Blur, Acrylic, Mica, Vibrancy (Made optional)
  • backgroundEffectColor: String, hex, rgb etc etc (Made optional)
  • background_effect_mica_dark Bool (Made optional defaults to false)

Happy to hold of this until the vibrancy package has improved to work on newer versions of Windows, and please let me know if any issues with code, not use to writing Rust so I apologize!

@veryard
Copy link
Contributor Author

veryard commented Nov 1, 2024

Todo:

  • since acrylic, mica, and macos vibrancy can potentially all take various config options, it'd make sense to have separate effects depending on os
  • Settings UI to have nice ui like attached
    image
    image

lars-berger pushed a commit that referenced this pull request Dec 15, 2025
A small PR that adds permissions for the frontend to use.

Specifically, adds ability to use window effects from the frontend
itself rather than the settings menu (still waiting for
#133), and the ability to make the
bar click-through.

I personally use these features in my Zebar configuration with a custom
Zebar build. I'd love to see these get added so there will be no need to
recompile Zebar to use my configuration.

<!--
Before submitting a PR, follow this checklist:

1. Give the PR a descriptive title.

  Examples of good titles:
    - fix: fix race condition in message loop
    - docs: update readme with new demo gif
    - feat: add new `general.focus_follows_mouse` config option

  Examples of bad titles:
    - fix #7123
    - update docs
    - fix bugs

2. If there is a related issue, reference it in the PR description, e.g.
closes #123.
3. Propose your changes as a draft PR if your work is still in progress.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📬 Needs triage

Development

Successfully merging this pull request may close these issues.

2 participants