Foreign-toplevel module doesn't show title when it's used by Labwc wayland compositor. #115

Closed
opened 2 months ago by AhmadRaniri · 4 comments

I heard about yambar update (foreign-toplevel module's added), I give it a try and I can't see window title shows. I use labwc wayland compositor and it supports wlr-foreign-toplevel. I have a luck with waybar. I don't know if it's yambar issue or labwc itself, still, I prefer yambar because it's more lightweight. Thanks.

I heard about yambar update (foreign-toplevel module's added), I give it a try and I can't see window title shows. I use labwc wayland compositor and it supports wlr-foreign-toplevel. I have a luck with waybar. I don't know if it's yambar issue or labwc itself, still, I prefer yambar because it's more lightweight. Thanks.
AhmadRaniri changed title from Foreign-toplevel module don't show title when it's used by Labwc wayland compositor. to Foreign-toplevel module doesn't show title when it's used by Labwc wayland compositor. 2 months ago
Owner

Have you checked if the same yambar config works in other compositors?

Can you post the output of

WAYLAND_DEBUG=1 yambar
Have you checked if the same yambar config works in other compositors? Can you post the output of ```sh WAYLAND_DEBUG=1 yambar ```
Owner

The major issue is that labwc calls the state() method without setting the ZWLR_FOREIGN_TOPLEVEL_HANDLE_V1_STATE_ACTIVATED bit (it does however appear to set the "minimized" and "maximized" bits correctly).

This means yambar considers all toplevels to be inactive. And, the example configuration only displays active toplevels.

A secondary issue is that labwc doesn't call the app_id() function. This means yambar will only display the window title, but not the name of the application (assuming the state() issue is resolved).

The major issue is that labwc calls the `state()` method without setting the `ZWLR_FOREIGN_TOPLEVEL_HANDLE_V1_STATE_ACTIVATED` bit (it does however appear to set the "minimized" and "maximized" bits correctly). This means yambar considers all toplevels to be **inactive**. And, the example configuration only displays **active** toplevels. A secondary issue is that labwc doesn't call the `app_id()` function. This means yambar will only display the window title, but not the name of the application (assuming the `state()` issue is resolved).
dnkl added the
invalid
label 2 months ago
dnkl closed this issue 2 months ago
Poster

Maximized and minimized option work, Thanks. Is it possible to add "on-click" operation?

Maximized and minimized option work, Thanks. Is it possible to add "on-click" operation?
Owner

Not atm. On-click currently support exec:ing external programs only, while this feature would require co-operation with the foreign-toplevel module. This is something that just isn't possible right now.

Not atm. On-click currently support exec:ing external programs only, while this feature would require co-operation with the foreign-toplevel module. This is something that just isn't possible right now.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.