-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scaled output messes up bar #2
Comments
Hi, thanks for the report! Lack of support for scaled outputs is currently a known limitation (levee, on which creek is based, didn't properly support this originally either). I don't use scaled outputs right now, hence it hasn't been a priority for me personally to address this. Additionally, it's not that easy to support in the current code base. One major problem in this regard is the lack of a good abstraction for fcft+pixman within the code base. Essentially, all calculations in I like the I am personally not a fan of config file support, but feel free to maintain you own fork if this is of interest to you. |
I see, thanks for the explanation. I understand your point about config. |
Thanks for tagging a new release, and allowing build with 0.12 zig.
I build and tried this on void linux, and it looks and feels quite nice.
One issue I encounter is that, for scaled output, the bar is messed up,
namely there's one more black bar below it.
By scaled, I mean
wlr-randr --output eDP-1 --scale 2
in river init.Also, it'd be nice to have a
-Dpie
configure option, to produce pie executables.Finally, what are your thoughts about implementing a config file?
instead of piping the output and/or poling frequently, the config file could contain
the actual command(s) I want to run, e.g
date '+%a %Y-%m-%d %H:%M'
,and their polling time, e.g. 5s,
as well as possibly the various options for font, color, etc,
similar to dwm but without the need to rebuild it.
The text was updated successfully, but these errors were encountered: