René D. Obermüller

Results 202 comments of René D. Obermüller

Ah, that makes sense. :) https://github.com/Alexays/Waybar/blob/79d3a1a2962cdad1ad02195916790ae1e63122c6/src/modules/wlr/taskbar.cpp#L280 Task initalises `content` with the bar orientation. `content` has child controls for the text before the icon, text after the icon, and the icon...

wlr/taskbar receives a list of app_ids (or changing app_ids) through [zwlr_foreign_toplevel_manager_v1.](https://wayland.app/protocols/wlr-foreign-toplevel-management-unstable-v1). Based on this app_id, wlr/taskbar looks for a matching .desktop file. If I had to guess, the app_id is...

If you have the config in a default location, you could just run `waybar -l debug` from command line. It starts a second. What you could also try try is...

I think you could try an app id mapping within wlr/taskbar config. Like this maybe? ``` "app_ids-mapping": { "chrome-bcngdmpegpihnheapppgoniglphkpfhm-Default": "io.github.ungoogled_software.ungoogled_chromium.flextop.chrome-bcngdmpegpihnheapppgoniglphkpfhm-Default" }, ```

Could be related to #3490, which has been merged. Can you try git master if you haven't already? Alternatively, you could try using the full path rather than ~.

Well, but it can be configured to be slim. ![satty-20240721-10:43:36](https://github.com/user-attachments/assets/623b50be-ccf3-4443-a377-50a0e08c76d8) ![satty-20240721-10:46:58](https://github.com/user-attachments/assets/fd481c24-a4f9-498e-96b7-19354d6cf5c8) This is a bar at the top, the grey stuff is just my background, so not really the waybar...

What's quite funny though, using ∫ (which reaches the bottom) changes the rendering. With it, Waybar needs at least 17 pixels, and there is some space within the label, not...

I can sort of reproduce the last bit with a minimal gtk4-rs application, which was largely copied from the [gtk4-layer-shell example](https://github.com/wmww/gtk-layer-shell/blob/master/examples/simple-example.c). As soon as I include ∫, the height of...

Reported at https://gitlab.gnome.org/GNOME/gtk/-/issues/7555

Have you tried GTK_DEBUG=interactive? ![waybar-tray-1](https://github.com/Alexays/Waybar/assets/29629287/e73ebf58-9d02-4250-b0e7-e294c55fc6de) ![waybar-tray-2](https://github.com/Alexays/Waybar/assets/29629287/484c2a40-5bd3-4a6e-9cba-d30972b4a147) What I can see here, the element with the name tray does get deactivated if indeed there aren't any children elements. Sometimes, I observe...