You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -169,7 +179,7 @@ java.lang.Thread in run at line 764
169
179
170
180
From a more specific [similar Error](https://github.com/msgpack/msgpack-java/issues/516) explaining FloatBuffer change in java 8 and in java 11.
171
181
172
-
We verifying that the jar files in android/libs/ are compiled for JRE11 (Major version 55),
182
+
We are verifying that the jar files in android/libs/ are compiled for JRE11 (Major version 55),
173
183
174
184
We think that the library being compiled against the JRE 11 runtime and osVersion 9 seems to use the Java 8 context where the classByteBuffer inherits the position method from Buffer and has a return type of java.nio.Buffer.
175
185
(On Java 11 the method is overridden with an implementation that returns java.nio.ByteBuffer.)
Copy file name to clipboardExpand all lines: Documentation/BasicUsage.md
+16-15Lines changed: 16 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Basic Usage
2
2
3
-
For starters we're going to import everything ready to use.
3
+
For starters, we're going to import everything ready to use.
4
4
Most of the included functionality is similar to how you would deal with WebRTC in your browser.
5
5
We support a lot of the official WebRTC APIs, see this [document](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection) for more details.
6
6
If you see functions that are listed in the document above but not listed below then they are likely not supported by this module yet and will most likely be supported in the near future, we're open to contributions.
@@ -41,7 +41,7 @@ You can also find a shim for react-native-web over [here](https://github.com/rea
41
41
42
42
## Get Available Media Devices
43
43
44
-
Some devices might not have more than 1 camera. The following will allow you to know how many cameras the device has. You can ofcourse use `enumerateDevices` to list other media device information too.
44
+
Some devices might not have more than 1 camera. The following will allow you to know how many cameras the device has. You can use `enumerateDevices` to list other media device information too.
45
45
46
46
```javascript
47
47
let cameraCount =0;
@@ -115,7 +115,7 @@ try {
115
115
## Destroying the Media Stream
116
116
117
117
Cycling all of the tracks and stopping them is more than enough to clean up after a call has finished.
118
-
You won't usually need to do this for remote tracks, only local.
118
+
You usually won't need to do this for remote tracks, only local.
119
119
120
120
```javascript
121
121
localMediaStream.getTracks().forEach(
@@ -142,7 +142,7 @@ let peerConstraints = {
142
142
143
143
## Creating a Peer Connection
144
144
145
-
Here we're creating a peer connection required to get a call started.
145
+
Here, we're creating a peer connection required to get a call started.
146
146
You can also hook up events by directly overwriting functions instead of using event listeners.
147
147
148
148
```javascript
@@ -170,8 +170,8 @@ peerConnection = null;
170
170
171
171
## Adding the Media Stream
172
172
173
-
After using one of the media functions above you can then add the media stream to the peer.
174
-
The negotiation needed event will be triggered on the peer connection afterwords.
173
+
After using one of the media functions above, you can then add the media stream to the peer.
174
+
The negotiation needed event will be triggered on the peer connection afterwards.
0 commit comments