https://bugs.winehq.org/show_bug.cgi?id=43765
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |quartz Summary|RSpec-Explorer windows are |RSpec-Explorer windows are |sometimes unresponsive to |sometimes unresponsive to |keyboard and mouse input |keyboard and mouse input | |(VideoWindow should not be | |run in separate thread)
--- Comment #4 from Zebediah Figura z.figura12@gmail.com ---
From the docs:
https://msdn.microsoft.com/en-us/library/windows/desktop/dd407349(v=vs.85).a...
"Normally, this filter's video window processes messages on a worker thread created by the Filter Graph Manager. Howerver, if an application directly creates the filter using CoCreateInstance, the video window processes messages on the application thread. In that case, the application thread must have a message loop, to dispatch messages to the video window. Also, the thread must not exit until the final Release call to the Video Renderer, which occurs when the Filter Graph Manager shuts down. Otherwise, the application might deadlock."
The application creates the VideoRenderer instance manually, but we don't handle that case and create a separate thread anyway.