You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could consider adding support for an empty AvailableData, which might help clean up some of the Python examples and avoid the need for some of the checks in the with statements.
Users won't have to worry about whether or not the runtime returns None and can just proceed with an iterator, empty or not.
The text was updated successfully, but these errors were encountered:
Closes#137.
- Change version string from 0.3.0 to 0.3.0-rc1.
- Updates acquire-core-libs and acquire-video-runtime submodules.
- Updates acquire-driver-zarr driver to v0.1.8 (bugfix release).
- Create an `AvailableData` struct on every call to
`runtime.get_available_data()`. It's no longer `Optional`, i.e., will
never be `None`.
🚨🚨 Potentially controversial decisions below 🚨🚨
1. Remove the unused `_store` field from `VideoFrame` struct. This was
causing `test_setup()` to fail when I did not explicitly delete frames
returned by the video frame iterator.
2. As a consequence of (1), the `store` field of
`VideoFrameIteratorInner` struct was unused, so I removed this as well.
3. As a consequence of both (1) and (2), the only place
`RawAvailableData` is used is as a member `inner` of `AvailableData`, so
I made `AvailableData.inner` an `Option<RawAvailableData>`, where it was
previously an `Option<Arc<RawAvailableData>>`.
See this comment:
Users won't have to worry about whether or not the runtime returns
None
and can just proceed with an iterator, empty or not.The text was updated successfully, but these errors were encountered: