[GH-ISSUE #1356] [Niri Taskbar] use official niri-ipc crate to display opened windows #4623

New issue

Open

opened 2026-05-23 00:54:45 +01:00 by JakeStanger · 1 comment

JakeStanger commented

2026-05-23 00:54:45 +01:00

Owner

Originally created by @n3ptune-plan3t on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1356

Is your feature request related to a problem? Please describe.

Right now, taskbar is showing apps according to their opening time. I want it according to how they are placed in workspace(left to right)

Describe the solution you'd like

I want the taskbar to show the opened apps according to how they are placed in workspace(left to right)
You can use niri-ipc crate

Originally created by @n3ptune-plan3t on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1356 **Is your feature request related to a problem? Please describe.** > Right now, taskbar is showing apps according to their opening time. I want it according to how they are placed in workspace(left to right) **Describe the solution you'd like** > I want the taskbar to show the opened apps according to how they are placed in workspace(left to right) > You can use niri-ipc crate

JakeStanger added the

M:Workspaces

T:Module Enhancement

A:Client

labels

2026-05-23 00:54:45 +01:00

JakeStanger commented

2026-05-23 00:54:46 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jan 30, 2026):

I'm not sure how feasible this is at the moment. The launcher module relies on the wlr-foreign-toplevel-management Wayland protocol, and not any IPC implementation. I can't see any plans to implement this sort of thing into any protocol, and relying on IPC results in doubling up the client code and having to pair the two.

There may be a better/easier way - open to suggestions.

@JakeStanger commented on GitHub (Jan 30, 2026): I'm not sure how feasible this is at the moment. The launcher module relies on the `wlr-foreign-toplevel-management` Wayland protocol, and not any IPC implementation. I can't see any plans to implement this sort of thing into any protocol, and relying on IPC results in doubling up the client code and having to pair the two. There may be a better/easier way - open to suggestions.