Closed kRHYME7 closed 4 months ago
@kRHYME7 yes that's something I've added yesterday to be able to re-use bindings from rofi.
Sorry, I should have put this behind an option flag. Will do in a bit...
If it's possible can we make this new feature arbitrary?(compatibility for older configs)
But any would still be cool.💪
Yes, I will set it opt-in. Given the speed a report came back, it looks like at least a few users prefer the current way :grin:
Thank you!
Rofi version (rofi -v or git commit in case of build issue)
1.7.5.wayland2.r213.gb847cb35-1
Configuration
even without configs https://gist.github.com/kRHYME7/4ed2a3f8a6b2b07a9bc64ef390d077d7
Theme
even without configs https://gist.github.com/kRHYME7/4ed2a3f8a6b2b07a9bc64ef390d077d7
Timing report
even without configs https://gist.github.com/kRHYME7/4ed2a3f8a6b2b07a9bc64ef390d077d7
Launch command
rofi
Step to reproduce
Expected behavior
Hyprland keybinding can still be executed even the rofi layer is rendered.
Actual behavior
I think rofi is prioritized for keyboard input.
Additional information
Downgrading to
1.7.5.wayland2.r211.g2ddef0f8-1
should provide the expected behavior.May I ask if this is a hyprland specific thing?
Should we add new/additional configuration for rofi?
Thanks in advance @lbonn 🙌
Using wayland display server protocol
I've checked if the issue exists in the latest stable release