The white flash when starting hyprland is a deal breaker for me
personally and I'd rather not have to deal with it. Should hopefully be
fixed in a later release since it seems to be a wlroots issue.
Although this was cute, there are simply too many bugs and other
inconveniences to be worth it. For example, the bar cannot be focused
when a workspace has a fullscreen application.
This is kinda cool however v0.27.2 and above appear to introduce a white
flash for me when starting Hyprland. Because of this, I'll probably stay
on v0.27.0 for the time being and only patch things I really want.
This was my test of the hyprbars fork. It turns out that the original
version is more useful, although both versions crash whenever reloading
the plugin after unloading it once.
By including an image changer in a separate exec-once, swww works as
intended. This enables virtual machines to have a random background on
startup without the abnormally long wait time previously.
This is unfortunately necessary to fix an issue where the external
monitor wouldn't update its state every few seconds. Not sure what the
issue is since this only occurs in applications when typing and not when
playing back video, for example.
Makes things simple and avoids having multiple ways to do the same
thing (launch applications).
Note that two dots are used here since at some point I presumably made
a wrapper inside a wrapper, which should probably be fixed later.
Instead of remembering which workspace an application is in, it's easier
to simply go to the previous or next workspace until reaching the desired
application.
This has the advantage of less keybinds used and no longer having to reach
across the keyboard when dealing with 6 or more workspaces.
Workspace state can be handled by ironbar's launcher instead, which has
the additional benefit of guaranteeing that you see all open applications.
hyprland-relative-workspace is used here for a GNOME-like workspace
experience. Hyprland's built-in m+1/m-1 would cycle the workspaces
instead of opening an empty one, and the recently merged r+1/r-1 does
not skip empty workspaces in-between other workspaces.
This was mainly useful on smaller screens where window contents took up
less space overall, however this makes it non-trivial to determine
whether or not gaps are enabled unless two or more windows exist in the
same workspace.
Since the gaps aren't an issue with larger screen sizes anyway, slightly
reducing gaps and disabling no_gaps_when_only seems like the play here.
