Feature: Hyde waybar style
This will use fzf to list out all styles in config.ctl and display in a list. When user clicks an entry, the style is applied
Right now we have to use Hyde waybar control and manually set the style to 1 . This will make it easier
Right now we have to use Hyde waybar control and manually set the style to
The waybar control is used to modify the modules, users needs to use keybindings to toggle waybar layouts.
This will use fzf to list out all styles in config.ctl and display in a list. When user clicks an entry, the style is applied
Yes, will try to do it.
You can create a Draft pr , I may provide some inputs
Similar feature I guess https://github.com/prasanthrangan/hyprdots/issues/1300
found a simple implementation https://github.com/AXWTV/Hyprland-DotFiles/blob/7a011d0e962b9ebcdc9ed51fa9c14eaf195fc042/config/hypr/configs/Keybinds.conf#L43
I peak on the implementation, but this is only for style not modules, right? It tries to select themes for static modules. (we can make it dynamic too).
My question is what do you really mean by "style" is it the css or the whole waybar layout?
whole waybar layout
@kRHYME7 here is a script maybe you can see how he is doing it https://github.com/JaKooLit/Hyprland-Dots/blob/main/config/hypr/scripts/WaybarStyles.sh
Can you help me modify and implement this on the wbarconfgent.sh and the wbarstylegen.sh
This one is for ` wbarconfgen.sh
conf_file="${WAYBAR_CONFIG:-$waybar_dir/config.jsonc}"
for the wbarsylegen.sh
out_file="${WAYBAR_STYLE:-$waybar_dir/style.css}"
You can test first by
ls now we got a custom generated waybar files
Now after having this minor change in the HyDE repo the CLI can now generete a configuration and css file somewhere where the CLI can just use it to preview the waybar configuration
I really forgot this thread, sorry.
Also I will try to open a feat req to rofi. If it's possible to run a command on hovered.
Sure
Can you help me modify and implement this on the wbarconfgent.sh and the wbarstylegen.sh
This one is for ` wbarconfgen.sh
conf_file="${WAYBAR_CONFIG:-$waybar_dir/config.jsonc}"for the wbarsylegen.sh
out_file="${WAYBAR_STYLE:-$waybar_dir/style.css}"You can test first by
lsnow we got a custom generated waybar filesNow after having this minor change in the HyDE repo the CLI can now generete a configuration and css file somewhere where the CLI can just use it to preview the waybar configuration
I really forgot this thread, sorry.
Sure . I will give it a try
Hey y'all did you manage to solve this issue? I can offer some help if it wasn't
Hi @austin4403 . I'm currently restructuring waybar right now. https://github.com/HyDE-Project/HyDE/pull/215#issuecomment-2674232109
It's not the same with the hyprdots repo. It's a structured way to navigate/share through layouts and styles.
Here's a sample API on how we manage things. Basically, users or ricers can create a whole waybar configuration. And store it in ./layouts as well as its style pair in ./styles. HyDE will provide presets and dynamic styles that can be imported on the configuration.
--Set
This way we can do e.g. --test <layout> and test a configuration. You get the Idea.
As for dynamic rofi preview this is now possible as of the latest rofi versions.
Oh, nice, that's great. BTW, is there a file in your system that configures Hyprland's touchpad, mouse, and keyboard settings? I couldn't find one, so I configured them manually in the userprefs. However, it feels redundant since some configurations, like input:sensitivity, don't seem to work, while others, like input:touchpad, function correctly. This inconsistency suggests a possible re-declaration of the config.
like input:sensitivity, don't seem to work, while others, like input:touchpad, function correctly. This inconsistency suggests a possible re-declaration of the config.
Hyprland set this stuff dynamically, and anything in userprefs can/will override the default config set by HyDE.
This inconsistency suggests a possible re-declaration of the config.
Probably but unlikely...
For HyDE project repo, all base configuration is set on this file ~/.local/share/hyde/hyprland.conf. Test this theory by editing this file. Also, Hyprland is known to not respect configuration sometimes, therefore you need to open an issue in hyprland GitHub.
IIRC, some input devices need to be declared explicitly, ( input category without device name is hit-and-miss ). See this https://wiki.hyprland.org/Configuring/Keywords/#per-device-input-configs
Oh thanks so much, I've fixed it. I just figured out that Hypyland must have changed the default force_no_accel to true for touchpads and this is responsible for the acceleration feature but fully takes over the controls like input:sensitivity I. I must have missed it in the docs. Thank you

