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

Why not texture view? #64

Closed
MHKalantarian opened this issue Jul 8, 2020 · 3 comments
Closed

Why not texture view? #64

MHKalantarian opened this issue Jul 8, 2020 · 3 comments

Comments

@MHKalantarian
Copy link

MHKalantarian commented Jul 8, 2020

I believe TextureView performance is way better than SurfaceView specially in fragments. So whats the reason behind using SurfaceView in this app?

Also when I tried to convert it to TextureView the Scanner Reticle in the middle will turn to black!
ScreenShot

@zhouyiself
Copy link
Collaborator

No particular reason I think, both could work for demo purpose and we didn't try out TextureView and do any performance measurement between them. So feel free to pull a request if one surpasses another obviously :)

@MHKalantarian
Copy link
Author

MHKalantarian commented Aug 3, 2020

No particular reason I think, both could work for demo purpose and we didn't try out TextureView and do any performance measurement between them. So feel free to pull a request if one surpasses another obviously :)

The problem is I tried to convert it, there is a problem in the reticle which I don't know where the problem is and will be glad if you or anybody else could help me out.

@cs-googler
Copy link

Hi, in general SurfaceView performs better and TextureView is compatible(less corner cases with bug) on more API levels.

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

No branches or pull requests

3 participants