Source slot IDs and capacities from config XML.
Slot IDs and capacities are defined in XML now. This allowes OEMs with
greater flexibility to override how many slots and how many affordances
can be in slot on the lock screen.
Our internal, shared library, still makes hard-coded assumptions about
there only being the expected number and IDs for slots, which is okay
since that code won't necessarily be used by OEMs.
Fix: 256195304
Test: Unit tests expanded
Change-Id: Ic2752e80cdda7495d3f03085597f3b995f461bda
diff --git a/packages/SystemUI/res/values/config.xml b/packages/SystemUI/res/values/config.xml
index 55d6379..40eb3e4d 100644
--- a/packages/SystemUI/res/values/config.xml
+++ b/packages/SystemUI/res/values/config.xml
@@ -804,4 +804,15 @@
<!-- Whether the device should display hotspot UI. If true, UI will display only when tethering
is available. If false, UI will never show regardless of tethering availability" -->
<bool name="config_show_wifi_tethering">true</bool>
+
+ <!-- A collection of "slots" for placing quick affordance actions on the lock screen when the
+ device is locked. Each item is a string consisting of two parts, separated by the ':' character.
+ The first part is the unique ID for the slot, it is not a human-visible name, but should still
+ be unique across all slots specified. The second part is the capacity and must be a positive
+ integer; this is how many quick affordance actions that user is allowed to add to the slot. -->
+ <string-array name="config_keyguardQuickAffordanceSlots" translatable="false">
+ <item>bottom_start:1</item>
+ <item>bottom_end:1</item>
+ </string-array>
+
</resources>