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

Added onPreviewStarted event and fixed some issues #104

Closed
wants to merge 7 commits into from
Closed

Added onPreviewStarted event and fixed some issues #104

wants to merge 7 commits into from

Conversation

Ninjaman494
Copy link

Related issues: #29 #92 #68

I also added an onPreviewStarted event to CameraListener which gets called when the Camera Preview has been drawn. In my app, I need a timer to start once the camera is displayed, so I needed this event to achieve this.

This is my first pull request, so if I did something wrong I apologize.

@andreas-
Copy link

+1

Output video was upside down when taken with the front camera in Portrait mode
@Ninjaman494
Copy link
Author

Orientation fix is the same as the one in this PR: #156

@austinkettner
Copy link
Member

Closing until a merge conflict resolution commit is in! Happy to merge is and reOpen this once available =)

# Conflicts:
#	build.gradle
#	camerakit-core/src/main/java/com/wonderkiln/camerakit/CameraView.java
#	camerakit/build.gradle
#	camerakit/src/main/api16/com/flurgle/camerakit/Camera1.java
#	camerakit/src/main/java/com/flurgle/camerakit/CameraListener.java
The Event Listening system has changed so much that my old implementation no longer works. My new implementation simply adds a new Event type and dispatches that Event right after startPreview is called.
@Ninjaman494
Copy link
Author

Sorry for the late response, it's been awhile since I've looked at this repo. I've fixed the merge conflicts and changed my implementation to work with the new Event system.

Moved the event dispatch to setupPreview. Before, the event wasn't triggered when the Camera is open and closed multiple times.
@austinkettner
Copy link
Member

Reviewing and will hopefully merge soon @Ninjaman494

@austinkettner
Copy link
Member

In favor of our massive refactor, if this issue still persist please make a new PR using the refined codebase. We definitely appreciate the help though! Just limiting merge conflicts and gathering support of testing/refinement/comments/feedback on the 1.0.0 PR.

#318

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants