Update README with known limitations

pull/54/head
Mattia Iavarone 8 years ago
parent fa65c5247e
commit dc475604c5
  1. 9
      README.md
  2. 2
      cameraview/src/androidTest/java/com/otaliastudios/cameraview/IntegrationTest.java

@ -57,6 +57,7 @@ compile 'com.otaliastudios:cameraview:1.2.1'
- [Permissions Behavior](#permissions-behavior) - [Permissions Behavior](#permissions-behavior)
- [Manifest file](#manifest-file) - [Manifest file](#manifest-file)
- [Roadmap](#roadmap) - [Roadmap](#roadmap)
- [Device-specific issues](#device-specific-issues)
## Usage ## Usage
@ -526,3 +527,11 @@ These are still things that need to be done, off the top of my head:
- [ ] add onRequestPermissionResults for easy permission callback - [ ] add onRequestPermissionResults for easy permission callback
- [ ] better error handling, maybe with a onError(e) method in the public listener, or have each public method return a boolean - [ ] better error handling, maybe with a onError(e) method in the public listener, or have each public method return a boolean
- [ ] decent code coverage - [ ] decent code coverage
## Device-specific issues
There are a couple of known issues if you are working with certain devices. The emulator is one of
the most tricky in this sense.
- Devices, or activities, with hardware acceleration turned off: this can be the case with emulators. In this case we will use SurfaceView as our surface provider. That is intrinsically flawed and can't deal with all we want to do here (runtime layout changes, scaling, etc.). So, nothing to do in this case.
- Devices with no support for MediaRecorder: the emulator does not support it, officially. This means that video/audio recording is flawed. Again, not our fault.

@ -33,7 +33,7 @@ import static org.junit.Assert.*;
*/ */
@RunWith(AndroidJUnit4.class) @RunWith(AndroidJUnit4.class)
@MediumTest @MediumTest
// @Ignore @Ignore
public class IntegrationTest extends BaseTest { public class IntegrationTest extends BaseTest {
@Rule @Rule

Loading…
Cancel
Save