Searched refs:handled (Results 1 – 25 of 57) sorted by relevance
123
50 How will this be handled?62 How will this be handled?69 `transformFeedbackRasterizationStreamSelect` handled?
26 images are handled.
20 writes are handled.
62 happens if that number is exceeded? Should this be handled by the driver
71 This could be handled by adding to a platform-independent acquire command a
150 The viewport swizzle feature performs the coordinate transformation handled
27 * IGnss start() & stop() - i.e. both requests must be handled independently,
32 This can commonly be handled by fixed function hardware, which allows identical behavior to the oth…
70 out of bounds and it handled by robustness with the usual rules.
42 * Image data with an invalid format must be handled gracefully in the same
37 * It means the success case may (or may not) be handled by the client in
760 bool handled = true; in getVertexAttribParameter() local797 handled = false; in getVertexAttribParameter()800 handled = false; in getVertexAttribParameter()803 return handled; in getVertexAttribParameter()
34 * handled by an external implementation-defined mechanism. Only
108 * Removes `validateBufferSize`, validation is instead handled by clients using metadata queries
92 * handled by calling ICameraDeviceCallback::notify(). In case of
207 * handling of the media (compressed and uncompressed) is handled within
95 * Information for requests that will be handled by offline session
85 * Image data with an invalid format must be handled gracefully in the same
26 * IGnss start() & stop() - i.e. both requests must be handled independently,
104 * handled by calling ICameraDeviceCallback::notify(). In case of
153 * Invalid format must be handled gracefully as if the field was missing.
203 /** Calls handled by the telephony stack (Eg: PSTN). */205 /** Calls handled by apps (Eg: Hangout). */
132 faults should be handled.170 faults that were returned will be handled as specified by
271 # client-state shall be handled locally by the encoder in most cases.272 # however, GL_CURRENT_VERTEX_ATTRIB and potential others are handled by the server side,442 # handled by encoder620 #client-state, handled by the encoder
123 * Service death is handled using `AIBinder_DeathRecipient` object which is linked to an interface