| /expo/packages/expo-face-detector/build/ |
| H A D | FaceDetector.d.ts | 109 accurate = 2 enumerator
|
| H A D | FaceDetector.js.map | 1 …accurate = 2,\n}\n\n// @docsMissing\nexport enum FaceDetectorLandmarks {\n none = 1,\n all = 2,\…
|
| /expo/packages/expo-face-detector/src/ |
| H A D | FaceDetector.ts | 119 accurate = 2, enumerator
|
| /expo/packages/expo-module-scripts/bin/ |
| H A D | expo-module-readme | 50 // This isn't really accurate, but these all behave the same as far as READMEs go
|
| /expo/packages/expo-face-detector/ios/EXFaceDetector/Utilities/ |
| H A D | EXFaceDetectorUtils.m | 27 @"accurate" : @(MLKFaceDetectorPerformanceModeAccurate)
|
| /expo/apps/native-component-list/src/screens/ |
| H A D | FaceDetectorScreen.tsx | 37 mode: FaceDetector.FaceDetectorMode.accurate,
|
| /expo/docs/pages/versions/v48.0.0/sdk/ |
| H A D | register-root-component.mdx | 75 {/* NOTE: This is only accurate if we land https://github.com/expo/expo/pull/18381 */}
|
| /expo/docs/pages/versions/v49.0.0/sdk/ |
| H A D | register-root-component.mdx | 75 {/* NOTE: This is only accurate if we land https://github.com/expo/expo/pull/18381 */}
|
| /expo/docs/pages/versions/v46.0.0/sdk/ |
| H A D | register-root-component.mdx | 75 {/* NOTE: This is only accurate if we land https://github.com/expo/expo/pull/18381 */}
|
| H A D | device.mdx | 197 … resolution (screen diagonal size), so the result may not be completely accurate. If the screen di…
|
| /expo/docs/pages/versions/v47.0.0/sdk/ |
| H A D | register-root-component.mdx | 75 {/* NOTE: This is only accurate if we land https://github.com/expo/expo/pull/18381 */}
|
| /expo/docs/pages/versions/unversioned/sdk/ |
| H A D | register-root-component.mdx | 75 {/* NOTE: This is only accurate if we land https://github.com/expo/expo/pull/18381 */}
|
| /expo/packages/expo-constants/build/ |
| H A D | ExponentConstants.web.js.map | 1 …(): number | null {\n // TODO: Bacon: The android version isn't very accurate either, maybe we …
|
| /expo/packages/expo-av/build/Audio/ |
| H A D | RecordingConstants.js.map | 1 …ed by iOS,\n * > in spite of appearing in the Apple source code. For an accurate list of formats s…
|
| /expo/packages/expo-device/build/ |
| H A D | Device.js.map | 1 …accurate.\n * If the screen diagonal length is between 3\" and 6.9\", the method returns `DeviceTy…
|
| /expo/ios/Exponent/Kernel/AppLoader/CachedResource/ |
| H A D | EXManifestResource.m | 168 // use commitTime instead of publishTime as it is more accurate;
|
| /expo/packages/expo-maps/build/ |
| H A D | Map.types.js.map | 1 … onLocationChangeEventInterval?: number;\n\n /**\n * Determines how accurate requests for loca…
|
| /expo/packages/expo-in-app-purchases/build/ |
| H A D | InAppPurchases.types.js.map | 1 …ring;\n /**\n * The type of the purchase. Note that this is not very accurate on iOS as this da…
|
| /expo/docs/pages/debugging/ |
| H A D | tools.mdx | 36 …ly on source maps. Unfortunately, these source maps are not always 100% accurate. In some cases, y…
|
| /expo/packages/expo-location/build/ |
| H A D | Location.types.js.map | 1 …ers. If the last known\n * location's accuracy radius is bigger (less accurate) then `null` is r…
|
| H A D | Location.js.map | 1 …n * and waits for a couple of updates, and then returns the one that is accurate enough.\n * @retu…
|
| /expo/packages/@expo/config-plugins/build/plugins/ |
| H A D | withIosBaseMods.js.map | 1 …eck / warn if a project actually exists, this'll provide\n // more accurate warning messages …
|
| /expo/ios/versioned-react-native/ABI49_0_0/Expo/ExpoKit/Core/Api/Components/Maps/ |
| H A D | ABI49_0_0AIRMapManager.m | 994 …// Calculation on float is not 100% accurate. If user zoom to max/min and then move, it's likely t…
|
| /expo/ios/versioned-react-native/ABI48_0_0/Expo/ExpoKit/Core/Api/Components/Maps/ |
| H A D | ABI48_0_0AIRMapManager.m | 1001 …// Calculation on float is not 100% accurate. If user zoom to max/min and then move, it's likely t…
|
| /expo/ios/Exponent/Versioned/Core/Api/Components/Maps/ |
| H A D | AIRMapManager.m | 994 …// Calculation on float is not 100% accurate. If user zoom to max/min and then move, it's likely t…
|