It seems the layout of the close and minimize button are hardcoded. That layout may not match other desktops, which results in a bad user experience on these systems.

I tried to compile it, but it ends with a "error[E0599]: no associated item named MAX found for type u32 in the current scope --> src/pulse.rs:133:23"
I also tried to install the deb-file. No success :) The binary also doesnt work, maybe Buster is too old?

Hey, I was looking into the options to package your application for Flathub, but I found that it's still quite rough around the corners.

One thing that's quite important, is a stand-alone build system. The most popular one is Meson, which uses Python to build and integrate a complete packaging system.

The best place to start, is by looking at another application that uses Meson in combination with Rust: https://gitlab.gnome.org/GNOME/fractal

With a build system like Meson, you can do the following things:

• Manage dependencies
• Manage localization
• Configure different build targets (release, production)
• Copy-paste files in their respective directories (/usr/share/ stuff like icons, metainfo and desktop shortcuts)

When using pipewire and pulseeffects, Myxer shows Unknown instead of pulseeffects for both outputs and inputs. Tested with pulseeffects-5.0.3 and pipewire-0.3.25.

Newer versions of Cargo no longer support empty version fields.

Closes #18, but the best approach would probably be to specify a version instead of *.

I tried to run clippy to find potential small improvements I could contribute. However, as hard tabs are used instead of spaces a lot of tabs_in_doc_comments issues are listed which makes it hard to find useful hints.

Using rustfmt the whole code can be formatted easily and in a way that is used for most other Rust projects.

Alternative

If you prefer to keep tabs, you could add a rustfmt.toml with

hard_tabs = true

To suppress the mentioned clippy warning, then #![allow(clippy::tabs_in_doc_comments)] should be added somewhere at the top of main.rs.

My Bluetooth sound card doesn't provide a device.description, leaving it as an "Unknown Card" on display; in other tools it shows just fine.

This PR adds a fallback sequence; it is not based on any good descriptions of these properties but on the observations made here (device.alias is the name I gave this in blueman, and thus is a slightly better name than device.name which is a hardware path for the built-in ones so should probably come last). It's not the sequence pavucontrol uses (pavucontrol shows the device.name over the device.alias), but it may ultimately be a matter of taste what to pick.

This PR adds a gtk class to the root window widget, which makes it possible to specifically address this application in GTK themes.

With Myxer's very minimal, beautiful looks it's a nice application to integrate into a customized desktop in a way that makes it feel native to the system, so putting focus on themability here seems like a great idea, in general!

Currently when an application is muted, the entire meter control is disabled. This is not always obvious on some themes. A muted application also behaves differently from one set to 0% volume when, in practice, this is effectively the same state.

I request that rather than the control be disabled on mute, the display state is set to 0% volume but the control is still left enabled. From this point pressing the mute/un-mute button would return the application to its previous volume level. Additionally simply moving the volume slider above 0% should also effectively 'un-mute' the application.

These changes remove the GTK headers from both the main window and Card Profiles popup, allowing a user's window manager to instead manage borders. This should resolve issue #15.

This now includes a fix for the out-of-place preference button.

Hello!

This PR adds a simple PKGBUILD to make it easier to install Myxer on Arch-based Linux distributions. It is based on releases, not on git commits. So, on every release, it should be updated. I'm not really experienced in creating PKGBUILDs, but I believe this one should work for most users.

Any suggestion is welcome and appreciated, of course.

I am very happy with the simplicity and functionality.... esp compared to pavucontrol. but I wish I could drag it to be much much smaller... What about no slider, and/or mouse wheel on the vol % also adjusts it. your thoughts?

Seemed after a bunch of press and interest there has not been any progress. As someone that doesn't "hate" but does dislike pavucontrol, it was my hope there was going to be an alternative. Myxer was just about there after all the press but not without any additions.

First of all thank you for this tool! It works flawlessly under WindowMaker, where my choices of mixers are a bit limited.

I haven't found this option, so pardon me if it already exists.

It would be great if it could be minimized into the tray. Even better if the mousewheel would still allow to change the master-channel while the application is minimized.

Thanks.

When running cargo build --release, the build fails with this message.

error: failed to parse manifest at `/home/mou/tmp/ebuild-temp/Myxer-1.2.1/Cargo.toml`

Caused by:
  failed to parse the version requirement `` for dependency `gio`

Caused by:
  unexpected end of input while parsing major version number