Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSDs? #192

Open
anarcat opened this issue Sep 13, 2023 · 2 comments
Open

OSDs? #192

anarcat opened this issue Sep 13, 2023 · 2 comments

Comments

@anarcat
Copy link

anarcat commented Sep 13, 2023

One thing I find interesting in the way I build my desktop I have noticed recently is that i try to cram everything in one status bar, which becomes unbearably big. That's not how modern desktops do things anymore, and there's a good reason: they pop up notifications based on actions. For example, you change the volume, you get a little slider/progress bar that relays the current state.

This is something that's not well supported in Wayland right now, or at least not in Sway, as far as I am concerned.

There's a bunch of options for this:

  • sway-notification-center kind of does this, but you'd need to wire up a keyboard short cut to pop it open and then keep it open while you push the backlight, might not work at all, and more designed for mouse-driven users
  • SwayOSD and Avizo are smaller and simpler, and just pop the notification, but they also to wrap around the keyboard shortcut to show the notification

There doesn't seem to be, in other words, something that just sits there and monitors for state changes and relays them in an overlay right now.

@ErikReider
Copy link
Contributor

There doesn't seem to be, in other words, something that just sits there and monitors for state changes and relays them in an overlay right now.

Having this in SwayOSD would make the OSD pop up when changing the volume in software, eg through Waybar or amixer which isn't desirable. That's why I went with the current keybinding-based implementation

@anarcat
Copy link
Author

anarcat commented Nov 22, 2023

Having this in SwayOSD would make the OSD pop up when changing the volume in software, eg through Waybar or amixer which isn't desirable. That's why I went with the current keybinding-based implementation

... why isn't this desirable? it's exactly what i want, in fact...

for now i've started using pasystray, thinking it was doing what i wanted (which is pop up an OSD when volume changes, regardless of the source), but it doesn't actually do that: it only pops up when you change the volume through the tray, which is far less optimal...

gianklug added a commit to gianklug/wearewaylandnow that referenced this issue Jul 21, 2024
Implements the suggestions from mpsq#192
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants