Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes flaky test with mpv 0.33.1 on ppc64el.
Closes #178.
|
|
Handling of c_void_p args (x11_display, wl_display) was broken.
Added a case to correctly handle the c_void_p constructor case.
See https://github.com/jaseg/python-mpv/issues/169
|
|
Closes #150
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This release introduces a new ShutdownError thrown in a few places in
case the underlying libmpv handle gets closed. Previously, such
situations would lead to hangs (wait_for_* methods) or segfaults (e.g.
__getattr__). Some of this carnage is still possible, but these
remaining issues will be closed over the next releases by throwing
ShutdownErrors in more places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The current mpv master changes default log output, breaking this test.
To be future-proof, it now emits its own message through the print-text
command.
|
|
|
|
The loop property was a poor choice here since setting it messes with
libmpv's event loop, leading to property change observer events being
dropped.
|
|
|
|
|