From @wildassoler :
Building a tool that needs a short numeric code entered (a product
barcode, up to 13 digits). LightTextInputEditor is great for text input,
but it's QWERTY-only — checked the light-keyboard source and don't see
a numeric layout mode anywhere.
For now I'm working around it with a plain Compose BasicTextField +
KeyboardType.Number/Phone, which triggers the user's own system IME's
numeric layout — but the visual style (and even whether a numeric layout
appears at all) then depends entirely on whatever keyboard app the user
has installed, rather than matching the consistent LightOS look
LightTextInputEditor gives for free. Tested with the stock AOSP keyboard
and it doesn't switch to a proper numeric layout either way.
Would a numeric-only layout option be something you'd consider adding to
light-keyboard / exposing via LightTextInputEditor? I'd guess other
tools that need PINs, quantities, or short codes would benefit too, not
just barcode entry.
via: lightphone/light-sdk#164
From @wildassoler :
Building a tool that needs a short numeric code entered (a product
barcode, up to 13 digits). LightTextInputEditor is great for text input,
but it's QWERTY-only — checked the light-keyboard source and don't see
a numeric layout mode anywhere.
For now I'm working around it with a plain Compose BasicTextField +
KeyboardType.Number/Phone, which triggers the user's own system IME's
numeric layout — but the visual style (and even whether a numeric layout
appears at all) then depends entirely on whatever keyboard app the user
has installed, rather than matching the consistent LightOS look
LightTextInputEditor gives for free. Tested with the stock AOSP keyboard
and it doesn't switch to a proper numeric layout either way.
Would a numeric-only layout option be something you'd consider adding to
light-keyboard / exposing via LightTextInputEditor? I'd guess other
tools that need PINs, quantities, or short codes would benefit too, not
just barcode entry.
via: lightphone/light-sdk#164