Popup display behaviour incorrect? [#7840]

[thebertster]

When a new track starts, the popup display, if configured, appears to show the track's name, album art etc.

However, if the track changes before the popup display's timeout (default 4 seconds?) is reached, the popup display is not updated.

This behaviour occurs if the track is changed in the player by any mechanism (assuming "only when inactive" is unchecked) but also if the previous/next track button is pressed on a multimedia keyboard (whether or not MM is active).

Often, I will have a web browser open with MM minimised and will use the multimedia keys on my keyboard to control MM without switching to it and I often use next track to skip quickly through tracks to find one I want to listen to. I should be able to do this visually using the popup display, but it is unusable for this purpose.

The behaviour I would expect is that if a new track is selected (by whatever means) and a popup display is already visible, the popup should be updated to reflect the new track and the display timeout should be reset. Should be a simple fix that will enhance usability enormously!

[alirezanoori]

I'm totally with you on this one. Winamp has this feature and I want MM to be superior to it like any other aspect in a multimedia player. As a matter of fact I've posted this request 2 times in the forum (without knowing that you've reported this). I hope developers fix this ASAP before MM4 hits the release build.
Best regards

[Dreadlau]

I agree with both of you.

[nohitter151]

reproduced and submitted: http://www.ventismedia.com/mantis/view.php?id=7840

[alirezanoori]

Thank you nohitter

[alirezanoori]

Any news on this? It's a long time since it is reported but it is not assigned yet. I'm afraid we hit the MM4 release before it gets fixed.

[Lowlander]

If there is nothing new in the Mantis entry there is no news.

[nohitter151]

Any news on this? It's a long time since it is reported but it is not assigned yet. I'm afraid we hit the MM4 release before it gets fixed.

It's a pretty minor issue, so I wouldn't be surprised if it were delayed until 4.1.

[alirezanoori]

I know it is minor but I don't think that getting it fixed would take that mich time. So it's really the matter of what is the priority for developers. Getting the minor issues out of the way in a very little time first and then work on the major issues which take much longer time or the other way around. I think in MM's case its the latter.

[Lowlander]

It might be a minor issue, but that doesn't always translate in a simple fix. A fix might require too many changes affecting other parts that it might not be doable this late in the beta cycle.

[alirezanoori]

@Lowlander: I'm a few years developer now, I'm perfectly aware of what you're talking about but I'm pretty sure that it doesn't take THAT much of change to fix this particular issue. Of course I don't have access to the source but I can guess. If this is not the case, you could say that the software's design is not good and I'm pretty sure that MM has a very good design (in software engineering's point of view).

[alirezanoori]

Thanks guys. It's fixed in 1384.