Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS X Bundle: Allow more than one instance of the player. #14

Closed
franzf opened this issue Jan 12, 2013 · 5 comments
Closed

OS X Bundle: Allow more than one instance of the player. #14

franzf opened this issue Jan 12, 2013 · 5 comments

Comments

@franzf
Copy link

franzf commented Jan 12, 2013

If you already have a file open on mpv.app, double clicking on another file to open it gives you this message:

Screen Shot 2013-01-12 at 2 58 16 PM

mpv 46f8429, compiled with Homebrew, OS X 10.8.2

@pigoz
Copy link
Member

pigoz commented Jan 12, 2013

With Cocoa you can't allow more than one instance of the player by simply spawning another process. Unfortunately the correct way would be implementing a "Document based" Cocoa application which I'm not sure how should interact with the playlist and wouldn't interact very well with the rest of mpv.

I think if you open a new file from the finder the player should use that file to replace the current playlist. That, at least, should be easier to implement.

@pigoz pigoz closed this as completed in 89a49ff Jan 16, 2013
@pigoz
Copy link
Member

pigoz commented Jan 16, 2013

The above commit doesn't allow more than one instance of the player, but allows to open new files in the current running instance.

@tewe
Copy link

tewe commented Feb 26, 2013

This throws away your playback position. A confirmation dialog would help.

@pigoz
Copy link
Member

pigoz commented Feb 26, 2013

mpv doesn't remember the playback position for any file, why it should in this case?

@tewe
Copy link

tewe commented Feb 26, 2013

No Mac app should lose state when Finder asks it to open a file. Either save the position or ask for confirmation before opening the new file, otherwise you break user expectations, which leads to frustration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants