QuickView Video Speaker icon

Started by ben, April 23, 2024, 07:18:02 PM

Previous topic - Next topic

ben

A really minor bug

In the QuickView video Mode the icons for the speaker both show a muted speaker symbol.

One should be indicating muted (e.g. with a small cross) and one not muted.

Mario

I see:

You cannot view this attachment.

Mute icon and muted icon.

sinus

Hmm, I agree with Ben, this is irritating. 
But I do not know, what other programs does. 

And yes, of course it is a minor thing. 
Best wishes from Switzerland! :-)
Markus

Mario

The first icon means: "Mute".
And when you click it or reduce the volume to zero, you get the 2nd muted / sound off icon

Not sure what causes the confusion....

sinus

I can only speak for me.
Both looks for me the same: mute.

The behaviour for example in YouTube is for me natural and logical.
There is a speaker icon, what is clear for me: sound is on.

If I click on this Speaker-icon, the sound it gone and the icon changes to muted and I know: no sound.

If I click a second time on this muted icon, the first appears again, and I know: again sound.

But I must say: I am really not a "video-expert". I saw only Ben's post, tried it and thought, well, yes, is not logical for me.

Best wishes from Switzerland! :-)
Markus

Mario

#5
So you want me to replace the "speaker X" icon (meaning: Mute) with a normal speaker icon? How would that represent that clicking it would mute the sound? It's just a symbol for a speaker without the X.
I could use the same icon, sans the X, to represent the muted state? Like so?

You cannot view this attachment.

Personally, I don't care.
I've drawn over 200 icons over the pasts months, and when more than two users want a different icon for this, I'll draw another one. I'm always open to suggestions.

I would not rate a "I don't like this icon" a bug, though. More like a feature request to re-consider the icon used.

This better?

You cannot view this attachment.

Not sure. YouTube uses the same icon but instead of an X they use a  variable "sound wave" to indicate volume (which IMatch does not do). For muted they use a similar "crossed out" speaker symbol to the one I use. I prefer the X since it means "delete/off/disable" in IMatch icon lore.


Tveloso

I think the question might be whether the icon should represent the state that we're currently in, or the state we'll go to when the icon is clicked.

I don't recall the specifics now, but I have managed to confuse myself on that very thing in the past...and it was on a text-based System, where a function key that acted as a toggle, had a single word to represent each state (so not even with icons - which tend to confuse me more).

Windows uses the "show current state" approach for the mute/unmute icons:

    You cannot view this attachment.

...so perhaps IMatch should use the same approach?...
--Tony

Mario

#7
YouTube uses this:

You cannot view this attachment.

Windows uses the speaker with the X to indicate a muted state, and a speaker with a "sound wave" to indicate unmuted state. That's probably more suitable for IMatch, being a Windows application. How about this:

You cannot view this attachment.

Let's see what the OP says. I'd like to close this ticket.

sinus

Quote from: Mario on April 24, 2024, 01:03:08 PMWindows uses the speaker with the X to indicate a muted state, and a speaker with a "sound wave" to indicate unmuted state. That's probably more suitable for IMatch, being a Windows application. How about this:


Let's see what the OP says. I'd like to close this ticket.

Yes, for me is this, what you proposed in your last post, very good. Clear for me. 
Exactly, I wonder, what the OP says. 
Best wishes from Switzerland! :-)
Markus

ben

Quote from: Mario on April 24, 2024, 01:03:08 PMYouTube uses this:

You cannot view this attachment.

Windows uses the speaker with the X to indicate a muted state, and a speaker with a "sound wave" to indicate unmuted state. That's probably more suitable for IMatch, being a Windows application. How about this:

You cannot view this attachment.

Let's see what the OP says. I'd like to close this ticket.
The last you posted is totally fine to me as well. It shows two different states.
And I agree, should have been a FR instead of a bug. Sorry about that.