-
Notifications
You must be signed in to change notification settings - Fork 16
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
Three issues on Android #29
Comments
I was able to address issue 3 (I think) but I still can't pause/resume or access a camera other than 0. Forcing an exit on_pause is a sort of workaround for issue 2 Resume, and index=1 are (I think) basic functionality, so I must be missing something basic.
|
can u do that on kivy camera ? i @RobertFlatt |
You don't say what "that" is, but Xcamera is a wrapper around Kivy camera so whatever "that" is, probably. A quick look at the code would have shown you this https://github.com/kivy-garden/xcamera/blob/develop/src/kivy_garden/xcamera/xcamera.py#L9 If you want to know what Kivy camera can do, look at the code https://github.com/kivy/kivy/blob/master/kivy/uix/camera.py#L36 |
yes i already try to change the index when the app is running and I got a pyjnius error @RobertFlatt |
I did somewhat fix the ISSUE 1 in my own project . I just added a index: 1 into the xcamera.kv file in example from https://github.com/kivy-garden/xcamera/tree/develop/src/kivy_garden/xcamera and also added a index: 1 into my own custom style.kv file calling the xcamera widget |
I gave up with Xcamera and wrote a new camera https://github.com/Android-for-Python/Camera4Kivy |
I had a similar situation. My laptop has an integrated camera (which actually includes 2: a RGB camera plus a IR camera), and a Logitech C170 webcam. OK for Googled serveral hours for a solution. Then I tried larger index values, and finally get all cameras working:
Yet I have no idea how those indices are assigned. So, the solution / workaround is to try different index values. |
Despite the issues, the code is a joy to read. :)
Example code (not as pretty as I would like because no on_camera_ready) , and log for the first issue follow:
Crash log
The text was updated successfully, but these errors were encountered: