Avizo had some issues that ultimately made me return to the old and
reliable dunst. For example, the home-manager service would fail to
restart after the computer was idle for a set amount of time.
The way avizo manages its window also resulted in compositors like
Hyprland and picom showing a blur artifact when avizo tried to fade
itself. Ultimately using dunst simplifies things and avoids having
to look in two different places for notifications.
mpdris2 seems to have much greater feature support than mpdris2-rs,
notably the inclusion of lower notification urgency by default and the
ability to start mpdris2 without it showing a stopped notification.
The biggest feature, however, is the possibility to run multiple
mpdris2 instances at the same time. This was impossible to achieve
with mpdris2-rs since it would claim that the bus was already taken.
Notably this enables much smoother usage when running mpdris2 in both
Hyprland and dwm at the same time. Combined with dunst, this enables
seamless notifications between the two environments.
Avizo seemingly has better support than swayosd in dwm, so this change
makes the OSD consistent across both environments.
Long-term it may be useful to figure out why swayosd would tile under
dwm and whether or not it'd be possible to fix upstream.
Note that glib was supposedly added for mounting-related things, but
this should be possible to upstream into the derivation instead if it
hasn't been added already.
Having to change the package list in two places was a bit redundant. We
can also use `with` patterns now since nixd warns if there are escaping
variables being used.
Note that variables used in multiple places are kept to make it easier
to recognize that those variables must be changed together. Also note
that inherit (pkgs) inside of mkMerge are currently kept to reduce the
diff.
- kanjidraw: Online alternatives with radicals etc. are better
- dmenu-wayland: Breaks with multiple monitors
- obs: Easier to use wf-recorder
- wallust: Easier to use stylix
Might be able to use swaync after all if I avoid using the mpris module
with it. This has the advantage of being supported by ironbar, which
would make missing notifications less likely.
This was my attempt at using the volume module, however I'd rather not
have to deal with using the small sliders that are extremely difficult
to see with the GTK theme I'm using.
I tried changing the colors with color, background, and border-color,
however I wasn't able to achieve the appearance I wanted, and disabling
the built-in popup results in a buggy left-clicking experience.
Will stop trying to make Hyprland work on mobile devices due to all the
issues with it for now.
For future reference, some issues include:
- Touch events not registering as touches, thus breaking applications
that have touch support like LibreWolf with FriendlyFox.
- OSK support in general being not there yet with the best keyboard
Squeekboard not working and wvkbd not being comfy enough to use.
- Screen size in general being small already so having multiple apps
side-by-side is mostly useless, especially when the OSK interferes
with this as well.
This worked but broke when changing the display from e.g. 200% scaling
to 100% scaling. Since being able to easily change the scaling of
Hyprland was one of the main reasons I wanted to try Hyprland over
Phosh, I don't really have a use case for Hyprland on touch devices at
this moment, especially with all the drawbacks of using it on such a
small screen and without hardware acceleration.
