LBCrion / sfwbar

S* Floating Window Bar
GNU General Public License v3.0
275 stars 17 forks source link

on sway, keyboard stops working after PopUp AutoClose #232

Open edwnh opened 1 month ago

edwnh commented 1 month ago

Minimal steps to reproduce:

  1. I'm using the latest git versions of both sway/wlroots and sfwbar
  2. In config file, enable autoclosing of the volume popup Function("SfwbarInit") { Config "PopUp 'XVolumeWindow' { AutoClose = true }" }
  3. Click the volume icon, to show a popup window.
  4. Click in any application. The popup will autoclose. But typing doesn't work in the focused application.

To get out of this state where typing doesn't work, it seems sufficient to use any keyboard shortcut that sway recognizes (e.g. mod+enter, mod+d, mod+2, ...).

Strangely, this doesn't seem to affect labwc.

LBCrion commented 1 month ago

This looks like a result of an unnecessary keyboard focus grab. It should be fixed in the latest git version. Can you please check if it works for you?

On Thu, 12 Sept 2024, 22:26 Edwin Huang, @.***> wrote:

Minimal steps to reproduce:

  1. I'm using the latest git versions of both sway/wlroots and sfwbar
  2. In config file, enable autoclosing of the volume popup Function("SfwbarInit") { Config "PopUp 'XVolumeWindow' { AutoClose = true }" }
  3. Click the volume icon, to show a popup window.
  4. Click in any application. The popup will autoclose. But typing doesn't work in the focused application.

To get out of this state where typing doesn't work, it seems sufficient to use any keyboard shortcut that sway recognizes (e.g. mod+enter, mod+d, mod+2, ...).

Strangely, this doesn't seem to affect labwc.

— Reply to this email directly, view it on GitHub https://github.com/LBCrion/sfwbar/issues/232, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASHPFFAVSHAIKTQS35HNOJLZWIBJRAVCNFSM6AAAAABOEDSKCOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDGMZYHEZTKMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

edwnh commented 1 month ago

Yes, it is fixed now. Thank you!