* fix: improve multi-monitor handling under wayland
When a monitor gets disconnected, the destroy event of all associated
windows gets called, and the window gets removed.
This patch changes that behavior: the window is still closed but the
configuration is kept using the existing reload mechanism.
In addition, a callback is added to listen for new monitors, triggering
a reload when a new monitor gets connected.
This logic also reloads already running windows, which has a positive and
negative effect:
- positive: if currently running e.g. on the second monitor specified in
the list, the window can get moved to the first monitor
- negative: if reloading starts it on the same monitor, it gets reset
(e.g. graphs)
I also had to work around an issue: the monitor model is not yet available
immediately when a new monitor callback triggers. Waiting in the callback
does not help (I tried 10 seconds). However, waiting outside, it always
became available after 10ms.
Tested with a dual monitor setup under KDE through a combinations of:
- enabling/disabling individual monitors
- switching between monitors
- specifying a specific monitor in the yuck config
- specifying a list of specific monitors in the yuck config
In all these cases the behavior is as expected, and the widget gets loaded
on the first available monitor (or stays unloaded until one becomes
available).
It also works when opening a window without any of the configured monitors
being available.
There is one remaining error from GTK when closing the window:
GLib-GObject-CRITICAL **: 20:06:05.912: ../gobject/gsignal.c:2684: instance '0x55a4ab4be2d0' has no handler with id '136'
This comes from the `self.gtk_window.disconnect(handler_id)` call. To
prevent that we'd have to reset `destroy_event_handler_id`.
* fix: do not call gtk::main_iteration_do while waiting for monitor model
Executors that poll a future cannot be called recursively (in this case
glib::main_context_futures::TaskSource::poll).
So we cannot call gtk::main_iteration_do here, which in some cases led to
the future being polled again, which raised a panic in the form of:
thread 'main' panicked at glib/src/main_context_futures.rs:238:56:
called `Result::unwrap()` on an `Err` value: EnterError
We can just remove it as tokio::time::sleep() ensures the main thread
continues to process (gtk) events during that time.
* add floor() and ceil() functions to simplexpr, akin to round()
* document addition of floor() and ceil()
* remove unnecessary second argument for floor() and ceil()
* Update documentation
---------
Co-authored-by: Martin Bogdanov <github () martinbogdanov.com>
* Revert "Force recreating windows on config change (#1284)"
This reverts commit 29fa1587c3.
* Revert "Avoid recreating windows when only duration changes (#1236)"
This reverts commit b6b7bc8453.
Fixes the regression from #1236 preventing hot reload.
This can be made granular, e.g. for changes that don't
effect all windows or css chnages not requiring a full
window restart
* feat: add raw-output arg to jq
Co-authored-by: Roman Hargrave <roman@hargrave.info>
* test: add some test cases for jq raw output
* refactor: improve run_jaq_function
* docs: document changes
---------
Co-authored-by: Roman Hargrave <roman@hargrave.info>
* feat: Add support for on-demand window focus on wayland
* fix: cargo fmt
* Update CHANGELOG.md with OnDemand focusable
* fix: add v0_6 feature to gtk-layer-shell in eww/cargo.toml
* Add changelog entry for transform-origin-properties
* Implement explicitly setting a center of rotation
The transform-Widget provides "rotate" to rotate its child. However, the
default center of rotation is (0, 0) (aka top-left), so it was not
possible to, for example, rotate a child in-place.
This commit implements the additional options `transform-origin-x` and
`transform-origin-y`. Both are optional, and the default value is 0.0 for
each, so previous configurations should produce the same results.
* Fix: transform order should be rotate->translate->scale
* add `EWW_BATTERY` support in (free|open|net)bsd
* add `EWW_BATTERY` support in (free|open|net)bsd
---------
Co-authored-by: ElKowar <dev@elkowar.dev>
* Add scss support for the ':style' widget property
* Add changelog entry for the scss support for the ':style' property
---------
Co-authored-by: ElKowar <dev@elkowar.dev>
* fix!: eliminate some dead code
* fix: fix lints
Combined diff of a7a09ea192b6f06b1984709029dc3bfe0481759e and bfc5cb9cb020dd256484eb5e4344e12e4a3b2ceb
Co-authored-by: Johan Geluk <johan@geluk.io>
* fix: remove unnecessary allow; fix capitalization
* chore: automatically update a few dependencies
* fix: fix lint
i introduced this in #1119, whoops
* docs: move #1132's changelog entry
---------
Co-authored-by: Johan Geluk <johan@geluk.io>
* Fix: EWW_NET wrong values for TX/RX stats
The sysinfo crate, structure Networks, basically caches one value of
total_received/total_transmitted each (as well as other metrics) and
returns the difference between those two values when queried via the
`received()` and `transmitted()` functions.
These values are updated by both the `refresh()` and `refresh_list()`
functions; so by calling both of them right after each other like
previously done here, sets both the cached total_received/... and the
current total_received/... to nearly the same value.
`refresh_list()` also updates the list of interfaces on a host, with a
marginally small performance impact for doing so (I measured slightly
more than 100 microseconds on my machine (0.1 milliseconds), around
20-25% more than with `refresh()`), especially considering this is run
only every 2 seconds.
* Add changelog entry for the EWW_NET bugfix
