This PR adds a helper function send_batch to komorebi-client that allows sending multiple messages in a batch. 3rd party users of this library could already do this themselves but it is nice to have this helper to simplify it.
Then, on komorebi-bar it makes use of the new send_batch function to batch all the messages in one go when pressing the button to move between workspaces or when moving between stacked windows.
Since we are creating this messages in one go we won't be mistakenly changing the value of mff for the user.
It also only batches the mff messages when the mff value it's true, if it is already false there is no need to be sending those extra messages.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/LGUG2Z/komorebi/pull/1175
**Author:** [@alex-ds13](https://github.com/alex-ds13)
**Created:** 12/14/2024
**Status:** ✅ Merged
**Merged:** 12/14/2024
**Merged by:** [@LGUG2Z](https://github.com/LGUG2Z)
**Base:** `master` ← **Head:** `fix/bar-changing-mff`
---
### 📝 Commits (2)
- [`3fee739`](https://github.com/LGUG2Z/komorebi/commit/3fee739318f16bcdd06f35ebcced7fdf29c82c3b) feat(client): create `send_batch` helper
- [`41af031`](https://github.com/LGUG2Z/komorebi/commit/41af0311169e1da7a6d80e148b92c2319478c226) fix(bar): prevent the bar from changing mff value
### 📊 Changes
**2 files changed** (+62 additions, -64 deletions)
<details>
<summary>View changed files</summary>
📝 `komorebi-bar/src/komorebi.rs` (+48 -64)
📝 `komorebi-client/src/lib.rs` (+14 -0)
</details>
### 📄 Description
This PR adds a helper function `send_batch` to komorebi-client that allows sending multiple messages in a batch. 3rd party users of this library could already do this themselves but it is nice to have this helper to simplify it.
Then, on komorebi-bar it makes use of the new `send_batch` function to batch all the messages in one go when pressing the button to move between workspaces or when moving between stacked windows.
Since we are creating this messages in one go we won't be mistakenly changing the value of `mff` for the user.
It also only batches the `mff` messages when the `mff` value it's true, if it is already false there is no need to be sending those extra messages.
<!--
Please follow the Conventional Commits specification.
If you need to update your PR with changes from `master`, please run `git rebase master`.
By opening this PR, you confirm that you have read and understood this project's `CONTRIBUTING.md`.
-->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/LGUG2Z/komorebi/pull/1175
Author: @alex-ds13
Created: 12/14/2024
Status: ✅ Merged
Merged: 12/14/2024
Merged by: @LGUG2Z
Base:
master← Head:fix/bar-changing-mff📝 Commits (2)
3fee739feat(client): createsend_batchhelper41af031fix(bar): prevent the bar from changing mff value📊 Changes
2 files changed (+62 additions, -64 deletions)
View changed files
📝
komorebi-bar/src/komorebi.rs(+48 -64)📝
komorebi-client/src/lib.rs(+14 -0)📄 Description
This PR adds a helper function
send_batchto komorebi-client that allows sending multiple messages in a batch. 3rd party users of this library could already do this themselves but it is nice to have this helper to simplify it.Then, on komorebi-bar it makes use of the new
send_batchfunction to batch all the messages in one go when pressing the button to move between workspaces or when moving between stacked windows.Since we are creating this messages in one go we won't be mistakenly changing the value of
mfffor the user.It also only batches the
mffmessages when themffvalue it's true, if it is already false there is no need to be sending those extra messages.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.