7) Every good media player refreshes the movie while dragging the mouse over the timeline with pressed mouse button. Why the Splash PRO updates the movie only after releasing the mouse button?
WMP12 doesn't do it too, Not good!
8) In case I disable the Loop feature, the movie should be paused at the last frame at the end of the playback.
It must stop the video, means unload the file, Not good!
10) Click to the movie screen should work as a pause/play while the double click should still work as enable/disable fullscreen. The best implementation is in MPC: If you double-click to the movie which plays, the first click pauses the movie and the second click starts the movie in a fraction of the second while enabling/disabling the fullscreen mode.
Pause/Play: Only Space key or the buttons.
Double-click: Fullscreen.
It's Splash not MPC, so Not good!
11) It would be nice to allow users to drag the player window while dragging by the movie screen.
Really bad idea. Splash team must remove it
Drag and Drop should be for ONLY the top window bar.
16) If you open a movie in the movie player, its window size should be automatically resized to display the movie in 100% (1:1).
The worst idea!
19) Pressing the ESC key in window mode should pause the playback and minimize the player (like in GOM).
ESC shouldn't do anything. It should be Space key to pause/play.
Minimize? Again, it's Splash not GOM.
22) In GOM player, I often press space and enter keys simultaneously to enable fullscreen and start playback OR to disable fullscreen and pause playback. Both keys works in Splash PRO player but for an unknown reason, pressing both keys at once will only accept the first key.
Space+Enter should do ONLY Fullscreen/De-fullscreen. In Splash, they added Enter key to do it too, so no problem
Space Key = Play/Pause
24) Often, if I drop a new movie into the SplashPRO player, the movie is played smoothly but for the first seconds without audio and the player is unresponsive. After few seconds the players will start responding normally.
EXACTLY! It's a bug that still exists in v1.10.0
Anyway, thanks for your feedback