| /system/media/camera/docs/ |
| metadata_properties.xml | 503 any flicker during the switch, the following procedure is recommended:
[all...] |
| docs.html | [all...] |
| /frameworks/base/core/java/android/hardware/camera2/ |
| CaptureResult.java | 582 * any flicker during the switch, the following procedure is recommended:</p>
[all...] |
| /external/chromium_org/components/policy/resources/ |
| policy_templates.json | 102 # recommended policies templates. This only affects the template generation;
103 # all policies can be at the recommended level. The default is False.
[all...] |
| /external/sqlite/dist/orig/ |
| sqlite3.c | [all...] |
| sqlite3.h | [all...] |
| /external/sqlite/dist/ |
| sqlite3.c | [all...] |
| sqlite3.h | [all...] |
| /external/qemu/ |
| qapi-schema.json | 96 # recommended that a unique name is used.
[all...] |
| /dalvik/docs/ |
| debugmon.html | 650 way it chooses. Big-endian byte ordering is recommended but not mandatory.
|
| /external/aac/libAACdec/include/ |
| aacdecoder_lib.h | 442 It is recommended to call the decoder with a AACDEC_CLRHIST flag to reset all states when
[all...] |
| /external/aac/libAACenc/src/ |
| aacenc.cpp | 634 * recommended settings, i.e. the audio quality is suboptimal anyway. Activating the crash
[all...] |
| /external/bison/darwin-lib/ |
| stdio.h | 753 fseek gets defined as a macro, it is recommended that the developer
[all...] |
| /external/bison/lib/ |
| stdio.in.h | 441 fseek gets defined as a macro, it is recommended that the developer
[all...] |
| /external/bison/linux-lib/ |
| stdio.h | 753 fseek gets defined as a macro, it is recommended that the developer
[all...] |
| /external/ceres-solver/docs/source/ |
| version_history.rst | 258 on non Android platforms. (This is NOT recommended).
|
| /external/ceres-solver/include/ceres/ |
| solver.h | 592 // highly recommended.
[all...] |
| /external/chromium_org/chrome/browser/resources/chromeos/chromevox/common/ |
| traverse_table.js | [all...] |
| /external/chromium_org/chrome/browser/resources/chromeos/chromevox/strings/ |
| chromevox_strings_en-GB.xtb | [all...] |
| /external/chromium_org/native_client_sdk/doc_generated/devguide/devcycle/ |
| debugging.html | 325 and other debugging information (see the <a class="reference internal" href="/native-client/devguide/devcycle/building.html#compile-flags"><em>recommended compile flags</em></a>).</p>
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/c/ |
| group___functions.html | [all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/cpp/ |
| classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p>
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_dev/cpp/ |
| classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p>
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/c/ |
| group___functions.html | [all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/cpp/ |
| classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p>
[all...] |
