Searched refs:significant (Results 1 – 13 of 13) sorted by relevance
313 bool significant = false; in IPlay_SetMarkerPosition() local318 significant = true; in IPlay_SetMarkerPosition()321 if (significant) { in IPlay_SetMarkerPosition()338 bool significant = false; in IPlay_ClearMarkerPosition() local344 significant = true; in IPlay_ClearMarkerPosition()347 if (significant) { in IPlay_ClearMarkerPosition()389 bool significant = false; in IPlay_SetPositionUpdatePeriod() local407 significant = true; in IPlay_SetPositionUpdatePeriod()410 if (significant) { in IPlay_SetPositionUpdatePeriod()
187 bool significant = false; in IRecord_SetMarkerPosition() local192 significant = true; in IRecord_SetMarkerPosition()195 if (significant) { in IRecord_SetMarkerPosition()212 bool significant = false; in IRecord_ClearMarkerPosition() local218 significant = true; in IRecord_ClearMarkerPosition()221 if (significant) { in IRecord_ClearMarkerPosition()
86 description: "Enabled significant place monitoring"
50 * Logs when the significant motion state changed. Motion is detected in the
8 * Usable when mmap'ed, so it doesn't take significant physical RAM
114 It also contains a significant amount of other UI that interacts with these
49 * significant motion
29 # app --> display latency, and unless significant testing is performed to avoid
448 * low memory pressure for a significant amount of time since last idle.
255 Whether this is true is especially significant if the work can be
282 # causing a significant performance penality.
348 # causing a significant performance penalty.
1858 * Logged when wifi detects a significant change in connection failure rate.5326 * Logs the wall-clock time when a significant wall-clock time shift occurs.13959 // significant change.