Pierre, I think you right here when you said this and perhaps it's this new 'precise frame stopping' feature that is causing these prolonged issues. Btw, myself or topic starter - never actually requested for this feature to exist. What I did mention, however, was a way to resolve the visual bug of the 'precise frame number' showing after clicking on the 'view' menu; post.xnview wrote:Is it useful to change frame number??
Additionally by showing the frame number it means that the name "Start/Stop" is not accurate but would indeed be more of a "Play/Pause".
So I think they are two options here:
1.> Just remove the precise frame number stopping altogether and go back to the previous method
2.> Keep the precise frame number method BUT allow a user to reset the frame number back to the first frame by likely double-clicking on the frame/frame area on the status bar AND ALSO a perhaps rename of the command to "Start/Pause"
Which of the two options you think? Or do you think of another better option.