diff options
author | wm4 <wm4@nowhere> | 2014-09-06 17:02:47 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-09-06 17:02:47 +0200 |
commit | 017b3fa9dbbed1bcd5711599e42513daf5009fd0 (patch) | |
tree | 12fcf673bdb3d08038c6d5ad67150238f866d0e4 /DOCS/man/lua.rst | |
parent | 348dfd93c4178633d3995a955045fafb7e9209d3 (diff) | |
download | mpv-017b3fa9dbbed1bcd5711599e42513daf5009fd0.tar.bz2 mpv-017b3fa9dbbed1bcd5711599e42513daf5009fd0.tar.xz |
lua: synchronously wait until scripts are loaded
This makes the player wait until each script is loaded. Do this to give
the script a chance to setup all its event handlers. It might also be
useful to allow a script to change options that matter for playback.
While waiting for a script to be loaded, the player actually accepts
input. This is needed because the scripts can execute player commands
anyway while they are being "loaded". The player won't react to most
commands though: it can't quit or navigate the playlist in this state.
For deciding whether a script is finally loaded, we use a cheap hack: if
mpv_wait_event() is called, it's considered loaded. Let's hope this is
good enough. I think it's better than introducing explicit API for this.
Although I'm sure this will turn out as too simplistic some time in the
future, the same would probably happen with a more explicit API.
Diffstat (limited to 'DOCS/man/lua.rst')
-rw-r--r-- | DOCS/man/lua.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/DOCS/man/lua.rst b/DOCS/man/lua.rst index d8791e7381..147563a964 100644 --- a/DOCS/man/lua.rst +++ b/DOCS/man/lua.rst @@ -47,6 +47,15 @@ The event loop will wait for events and dispatch events registered with ``mp.register_event``. It will also handle timers added with ``mp.add_timeout`` and similar (by waiting with a timeout). +Since mpv 0.6.0, the player will wait until the script is fully loaded before +continuing normal operation. The player considers a script as fully loaded as +soon as it starts waiting for mpv events (or it exits). In practice this means +the player will more or less hang until the script returns from the main chunk +(and ``mp_event_loop`` is called), or the script calls ``mp_event_loop`` or +``mp.dispatch_events`` directly. This is done to make it possible for a script +to fully setup event handlers etc. before playback actually starts. In older +mpv versions, this happened asynchronously. + mp functions ------------ |