Micro player becomes unresponsive [#17072]

[Deadcool]

This seems to happen after an unspecified time of MM5 being minimized to Micro Player. Clicking the Restore button on the micro player does nothing, nor do any of the other controls in the micro player respond.

I can Restore the application from the notification bar icon, but if I select minimize to Micro Player again, it disappears (i.e. micro player does not show up on the task bar.) Right-click on MM5 icon in notification bar continues to function.

If I close MM5 completely and re-open, micro player works as designed again (seems like something gets re-initialized?)

[Lowlander]

Which Build (Help > About) are you seeing this with?

[Deadcool]

Which Build (Help > About) are you seeing this with?

5.0.1.2433

[Lowlander]

Can you please try with the latest beta of 5.0.2: viewtopic.php?f=30&t=86639&sd=d

and if it still fails, capture this problem in a debug log (step 4b) and attach the log to a Support Ticket: viewtopic.php?f=30&t=86643

This will help a developer analyze why this occurs on your setup.

[Deadcool]

It's actually worse in the 5.0.2.2507 beta, the micro player disappears right after minimizing to it the very first time.

Debug log and screen capture included in ticket 2864.

[Deadcool]

Issue is still present in build 2508 (beta).

[Deadcool]

The support ticket for this was submitted a week ago and is still in "Awaiting Agent" status, is there a timeframe for support?

[Lowlander]

It's being worked on as: https://www.ventismedia.com/mantis/view.php?id=17072

[Deadcool]

This was listed as one of the bugs to be resolved in 5.0.3, however in the just-released beta version it's not working consistently.

On first opening MM5, playing a track then selecting the Micro player, micro player does not appear on the taskbar (previously reported bug.)

If the application is Restored from the icon in the icon bar, then micro player is selected, it DOES work. So behavior is inconsistent.

Build 5.0.3.2600

[Lowlander]

The bug trackers shows it hasn't been resolved yet, it does have a target for 5.0.3, but 5.0.3 is still in early testing.