-
Notifications
You must be signed in to change notification settings - Fork 856
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
Adding getters and setters in VideoCaptureWrap #559
base: master
Are you sure you want to change the base?
Conversation
…FrameAt to SetPositionMS
Codecov Report
@@ Coverage Diff @@
## master #559 +/- ##
=========================================
- Coverage 51.19% 50.9% -0.29%
=========================================
Files 34 34
Lines 3899 3929 +30
Branches 27 27
=========================================
+ Hits 1996 2000 +4
- Misses 1903 1929 +26
Continue to review full report at Codecov.
|
Looks great, any chance you could add an example file or some tests? Thanks! |
I have never done that before as I am not a professional :-), but I will look into it. |
hi fakob - in terms of a test, copy an existing example (e.g. examples/motion-track.js), and make it access each of the getters/setters in VideoCapture - this should be enough to ensure that they get tested regularly, and should contribute to coverage percentage. I just did that for examples/bgsubtractor.js ; if you want another video-reading sample to look at. |
Hi,
I have added getPosition, getPositionMS, getFPS, getFourCC and setPositionMS.
setPositionMS is a duplicate of getFrameAt, but as it sets the position in MS I find getFrameAt confusing and would deprecated that in the future.
What do you think?