Home
last modified time | relevance | path

Searched refs:nesting (Results 1 – 6 of 6) sorted by relevance

/frameworks/base/services/core/java/com/android/server/
DAlarmManagerService.java565 int nesting; field in AlarmManagerService.FilterStats
581 int nesting; field in AlarmManagerService.BroadcastStats
982 if (fs.nesting > 0) pw.print("*ACTIVE* "); in dumpImpl()
1002 if (bs.nesting > 0) pw.print("*ACTIVE* "); in dumpImpl()
1017 if (fs.nesting > 0) pw.print("*ACTIVE* "); in dumpImpl()
1645 if (bs.nesting == 0) { in deliverAlarmsLocked()
1646 bs.nesting = 1; in deliverAlarmsLocked()
1649 bs.nesting++; in deliverAlarmsLocked()
1653 if (fs.nesting == 0) { in deliverAlarmsLocked()
1654 fs.nesting = 1; in deliverAlarmsLocked()
[all …]
DAppOpsService.java123 public int nesting; field in AppOpsService.Op
714 if (op.nesting == 0) { in startOperation()
719 op.nesting++; in startOperation()
748 if (op.nesting <= 1) { in finishOperationLocked()
749 if (op.nesting == 1) { in finishOperationLocked()
755 + " duration=" + op.duration + " nesting=" + op.nesting); in finishOperationLocked()
757 op.nesting = 0; in finishOperationLocked()
759 op.nesting--; in finishOperationLocked()
/frameworks/base/docs/html/training/improving-layouts/
Doptimizing-layout.jd40 lead to an excessively deep view hierarchy. Furthermore, nesting several instances of {@link
143 <li>Deep layouts - Layouts with too much nesting are bad for performance. Consider using flatter la…
/frameworks/base/core/java/android/widget/
DEditor.java1090 int nesting = ++ims.mBatchEditNesting; in beginBatchEdit() local
1091 if (nesting == 1) { in beginBatchEdit()
1113 int nesting = --ims.mBatchEditNesting; in endBatchEdit() local
1114 if (nesting == 0) { in endBatchEdit()
/frameworks/base/docs/html/training/basics/network-ops/
Dxml.jd339 track of the nesting depth.</li>
/frameworks/base/docs/html/guide/topics/ui/
Dmenus.jd836 <p>You can create a group by nesting {@code &lt;item&gt;} elements inside a {@code &lt;group&gt;}