Apologies in advance for screen entity terminology - I am yet to find a section of the Help which labels the screen components that I will be describing. If someone would like to correct my terminology, I'd happily provide a more cogent explanation.
I am using the Material Design skin, the default I think. The bottom of the MM screen has an orange bar about 1.5cm high containing play controls, topped by a thin line that (I'll call that the 'play progress line') hosts a dot indicator ('play progress dot') of how much of the track has been played. I'm well versed in using the mouse to click on that dot and move it along the line to change what part of the song is being played.
My problem is that I've had several instances now - two in my last session - where a mouse pointer movement across the play progress line has caused the play progress dot to relocate without me clicking on it. This is a significant inconvenience when using the player for public purposes.
The uncommanded play point change only seems to happen if the mouse pointer passes close to the play progress dot, and, no, I don't have the mouse pointer held down when that happens, and no I don't get any other anomalous mouse selection events in other apps or windows that would indicate that the mouse is at fault. This happens to tracks that I have not interacted with except to initiate their play. I have examined the last two incidents with some interesting correlations:
- Both occurred at about the 3 minute mark (2:59ish) about 2/3rds through each track, and
- Both jumped forward about 10 secs, and
- In both cases the line of the mouse pointer movement (diagonal down to left) passed within about 3cm of the position of the play progress dot. This is because I was taking the mouse pointer down to the orange bar to right click for the stop after current track option.
My workaround is to try to have the mouse pointer track avoid the play progress dot unless I intend to move it (unlikely in public use). But this is a rare occurrence anyway so I'll look out for other instances and will advise if it does occur again.
Cheers
Matt