Bug #290
Will not open video after closing another
| Status: | Closed | Start Date: | 02/01/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assigned to: | % Done: | 0% |
||
| Category: | gui_controls | |||
| Target version: | rev14 |
Description
New Rev13 (1310) Open one file and it plays. Close it and try to open another and nothing happens. Nothing even happens in the log when you try to open a new file.
History
Updated by Kevin Dean about 2 years ago
There's an issue where it won't open a video if the player window is closed completely. Try File-->New Player and then open the video for now.
Updated by anon anon about 2 years ago
Yup, happens for me as well, it appeared in Rev13-Test8, I guess it wasn't fixed before Rev13 was released.
Rev13-Test7 does not have this problem.
I'm not upgrading from Rev13-Test7 until this is fixed, since Mplayer OSX Extended keeps running even when the video is closed, unless it's manually shut down.
Updated by anon anon about 2 years ago
Same thing if you want to drag/drop a video to the dock icon or do "File, Open..." or "File, Open Recent", you need to use "File, New Player" or "Window, Show Main Player" before any of these actions are possible.
Just the simple act of double clicking on a video file from the finder, dragging a video file to the Mplayer OSX Extended icon on the dock or doing "File, Open..." or "File, Open Recent" should trigger a new player window to accommodate the new file being opened. And if one is already being used for playback, either play the new file in the existing player window or spawn a new one. And make it a preference for the user to choose which behavior is wanted.
Or if that's not possible, simply leave the last player window open at all times, as in, while Mplayer is running, never close the player window even when there is nothing playing.
Updated by Adrian Stutz almost 2 years ago
- Category changed from video_output to gui_controls
- Status changed from New to Assigned
- Priority changed from Immediate to High
- Target version changed from rev13 to rev14
Probably an issue with the new support for multiple player windows. I suspect the open message gets sent to a nil object.
Updated by Adrian Stutz almost 2 years ago
- Status changed from Assigned to Closed
Fixed in rev14-test2.