JakeStanger/ironbar

Fork 0

mirror of https://github.com/JakeStanger/ironbar.git synced 2026-07-11 13:15:20 +01:00

[GH-ISSUE #633] [Launcher] Items overflow offscreen #5833

New issue

Closed

opened 2026-05-23 01:53:16 +01:00 by JakeStanger · 5 comments

JakeStanger commented

2026-05-23 01:53:16 +01:00

Owner

Originally created by @humaidq-tii on GitHub (Jun 5, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/633

Describe the bug
When using Launcher module with show_names enabled, applications with long title names let ironbar go offscreen.

To Reproduce
Steps to reproduce the behavior:

Enable launcher module with show_names.
Open some applications, maybe a browser window with a webpage that includes a long title.
Your ironbar will start going off-screen

Expected behavior
Title name should be truncated at least, and if still overflows, module should be scrollable without resizing entirety of ironbar.

System information:

Distro: NixOS 24.05
Compositor: labwc
Ironbar version: 0.15.1

Configuration
anchor_to_edges is set to true, and margins are added (200 on left & 200 right).
Some basic styling is also added.

Originally created by @humaidq-tii on GitHub (Jun 5, 2024). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/633 **Describe the bug** When using Launcher module with `show_names` enabled, applications with long title names let ironbar go offscreen. **To Reproduce** Steps to reproduce the behavior: 1. Enable launcher module with `show_names`. 2. Open some applications, maybe a browser window with a webpage that includes a long title. 3. Your ironbar will start going off-screen **Expected behavior** Title name should be truncated at least, and if still overflows, module should be scrollable without resizing entirety of ironbar. **System information:** - Distro: NixOS 24.05 - Compositor: labwc - Ironbar version: 0.15.1 **Configuration** `anchor_to_edges` is set to `true`, and margins are added (200 on left & 200 right). Some basic styling is also added.

JakeStanger closed this issue

2026-05-23 01:53:16 +01:00

JakeStanger commented

2026-05-23 01:53:16 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jun 28, 2024):

Thanks for reporting. I've got some fixes & improvements around the truncation system in the works for this, including more sensible defaults.

I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again.

@JakeStanger commented on GitHub (Jun 28, 2024): Thanks for reporting. I've got some fixes & improvements around the truncation system in the works for this, including more sensible defaults. I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again.

JakeStanger commented

2026-05-23 01:53:16 +01:00

Author

Owner

@crimsonduelist commented on GitHub (Jun 29, 2024):

I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again.

What about a X number of items specified and and then buttons to go through sections. Like windows does. Or would that count as scrollable also?

@crimsonduelist commented on GitHub (Jun 29, 2024): > I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again. What about a X number of items specified and and then buttons to go through sections. Like windows does. Or would that count as scrollable also?

JakeStanger commented

2026-05-23 01:53:16 +01:00

Author

Owner

@ToxicMushroom commented on GitHub (Nov 9, 2024):

Can also go onto the next screen and obstruct windows ect, not sure how other bars handle this or what the best solution is.

@ToxicMushroom commented on GitHub (Nov 9, 2024): ![image](https://github.com/user-attachments/assets/607c44da-8ccf-4687-9f8e-a80c737475ec) Can also go onto the next screen and obstruct windows ect, not sure how other bars handle this or what the best solution is.

JakeStanger commented

2026-05-23 01:53:16 +01:00

Author

Owner

@huyufeifei commented on GitHub (Jan 23, 2025):

Thanks for reporting. I've got some fixes & improvements around the truncation system in the works for this, including more sensible defaults.

I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again.

hello, thanks for your great work!
I encountered this problem too while using a custom label module with dynamic length. Is it possible to add truncate related option for this module?

@huyufeifei commented on GitHub (Jan 23, 2025): > Thanks for reporting. I've got some fixes & improvements around the truncation system in the works for this, including more sensible defaults. > > I don't think making the module scrollable is easily feasible or a nice UX, but hopefully it'll never get to the point where that's necessary again. hello, thanks for your great work! I encountered this problem too while using a custom label module with dynamic length. Is it possible to add `truncate` related option for this module?

JakeStanger commented

2026-05-23 01:53:16 +01:00

Author

Owner

@JakeStanger commented on GitHub (Feb 21, 2025):

Hello, finally got to finishing this!

What about a X number of items specified and and then buttons to go through sections. Like windows does. Or would that count as scrollable also?

It's a little clunky, but I've gone this route. There is a new configurable page_size option (defaults to 1000 so it won't show). Once the item count exceeds the page size, forward/back arrows will show which step through "pages" of the items.

I did have a look at proper scrolling but it seems like it'd be a right faff and bit of a hack to get GTK to even think about doing that.

I encountered this problem too while using a custom label module with dynamic length. Is it possible to add truncate related option for this module?

@huyufeifei It only took a couple of mins so I've added truncate options to the label module and custom module while I was at it.

Should all be landing soon.

Can also go onto the next screen and obstruct windows ect, not sure how other bars handle this or what the best solution is.

I wasn't able to replicate this one so I'm assuming it's compositor-specific. Not sure what the correct behaviour is here but I would assume it's its responsibility to cap it. I may be able to force GTK if it's still an issue.

@JakeStanger commented on GitHub (Feb 21, 2025): Hello, finally got to finishing this! > What about a X number of items specified and and then buttons to go through sections. Like windows does. Or would that count as scrollable also? It's a little clunky, but I've gone this route. There is a new configurable `page_size` option (defaults to 1000 so it won't show). Once the item count exceeds the page size, forward/back arrows will show which step through "pages" of the items. I did have a look at proper scrolling but it seems like it'd be a right faff and bit of a hack to get GTK to even think about doing that. > I encountered this problem too while using a custom label module with dynamic length. Is it possible to add truncate related option for this module? @huyufeifei It only took a couple of mins so I've added truncate options to the `label` module and custom module while I was at it. Should all be landing soon. > Can also go onto the next screen and obstruct windows ect, not sure how other bars handle this or what the best solution is. I wasn't able to replicate this one so I'm assuming it's compositor-specific. Not sure what the correct behaviour is here but I would assume it's its responsibility to cap it. I may be able to force GTK if it's still an issue.