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

Handle external image life time in api.delete_image() call #636

Merged
merged 3 commits into from Dec 28, 2016

Commits on Dec 28, 2016

  1. Extend the ExternalImageHandler callback functions

    Now, the ExternalImageHandler has lock(), unlock() and release() callback functions.
    Use lock() instead of get() callback in WR render update_deferred_resolves().
    JerryShih committed Dec 28, 2016
  2. Handle the releasing of external images in api.delete_image().

    Release the external images when a new frame is ready.
    Merge ResultMsg::UpdateTextureData and NewFrame::NewFrame message into one message.
    JerryShih committed Dec 28, 2016
  3. Show panic if we try to call update() for external image.

    JerryShih committed Dec 28, 2016
You can’t perform that action at this time.