Searched refs:spot (Results 1 – 9 of 9) sorted by relevance
271 Spot* spot = getSpotLocked(id); in setSpots() local272 if (!spot) { in setSpots()273 spot = createAndAddSpotLocked(id); in setSpots()276 spot->updateSprite(&icon, x, y); in setSpots()281 Spot* spot = mLocked.spots.itemAt(i); in setSpots() local282 if (spot->id != Spot::INVALID_ID in setSpots()283 && !spotIdBits.hasBit(spot->id)) { in setSpots()284 fadeOutAndReleaseSpotLocked(spot); in setSpots()441 Spot* spot = mLocked.spots.itemAt(i); in doAnimate() local442 if (spot->id == Spot::INVALID_ID) { in doAnimate()[all …]
180 void releaseSpotLocked(Spot* spot);181 void fadeOutAndReleaseSpotLocked(Spot* spot);
53 from the same spot.</p>
162 One of the best ways to spot issues to resolve is by measuring user behavior.
222 on a blank spot on the Home screen, a Context menu appears; selecting
911 watching reviews, you can spot technical issues that may affect users in
760 to create, rather than aiming for any particular spot on the list.</p>
660 to create rather than aiming for any particular spot on the list.</p>
155 <strong>meminfo tool</strong> is enhanced to make it easier to spot memory