# Map Jianlai’s input controls across two actual iPad space states

Language: en
Canonical: [Map Jianlai’s input controls across two actual iPad space states](<https://allluckly.cn/en/guides/jianlai-ipad-space-input-control-map/>)
中文：[中文 HTML](<https://allluckly.cn/guides/jianlai-ipad-space-input-control-map/>)
English: [English HTML](<https://allluckly.cn/en/guides/jianlai-ipad-space-input-control-map/>)
Published: 2026-11-16T00:00:00+08:00
Modified: 2026-11-16T10:04:36+08:00
Author: Bison

Hold a text card, theme and input scheme fixed while comparing reachable controls and retained text, without assuming split or floating keyboards.

English translation of the [Chinese original](<https://allluckly.cn/guides/jianlai-ipad-space-input-control-map/>), translated on 2026-11-16. Original publication dates, attribution, code and version notes are retained.

Hold a text card, theme and input scheme fixed while comparing reachable controls and retained text, without assuming split or floating keyboards.

## 1. Identify the device and onscreen keyboard

Published information and official tablet screenshots establish Jianlai’s iPad scope, not identical keys or floating/split keyboards in every window. Open an ordinary note and confirm visible Jianlai rather than an external keyboard or system input method. Record version, orientation and opening state. Without a tablet, retain preparation instead of borrowing a screenshot. If the onscreen keyboard is unavailable, keep the comparison pending rather than reset accessories. This checks visible input, not external-keyboard shortcuts.

## 2. Fix a nonsensitive text card

Use target `资料卡 A7，数量12。` as practice, not inventory/business data. Preserve it separately from results, with recognisable Chinese, Latin/digit and punctuation references. Fix theme, size, language and Chinese layout rather than attribute a nine-to-26-key change to space. Wrapping can change without changing the card’s identity; do not shorten it for a neat screenshot. Preserve notes/settings and keep the same target and host throughout.

## 3. Choose two space states actually available

Choose two reversible orientations/window states supported by the current device, labelled A/B. Apple’s system-keyboard examples do not promise identical Jianlai gestures or floating sizes. A host preventing rotation/resizing limits the comparison; complete the baseline without claiming a second state. Use real state names instead of invented logical-width thresholds or extra-key-row guarantees. Change one space condition while retaining the original input scheme.

## 4. Map four controls in A

In A identify candidates, deletion, digits/symbol switching and return-related controls, recording relative positions rather than only screen coordinates. An absent control stays unobserved. Enter/commit the card and observe one ordinary deletion/restoration, checking actions and text separately. This maps reachability, not every touch target. A larger display does not establish faster typing or fewer errors. Save A before changing space so the baseline remains clear.

## 5. Re-identify controls in B instead of reusing coordinates

In B wait for stability, confirm Jianlai/original scheme and re-identify the four controls. Record moved or unchanged positions without requiring rearrangement everywhere. Do not tap old coordinates blindly. If the host also changes field type, record that extra condition and return to the ordinary note rather than treat a system numeric field as Jianlai’s layout. Keep document, input method and available area identified together.

## 6. Separate retained text from keyboard presentation

After committing in B, check Chinese, identifier, quantity and punctuation, then return to A and inspect retained text. Larger/wider keyboard labels do not style or synchronise the document. Wrapping can change while characters and stored boundaries need their own checks. Record interrupted composition during rotation rather than call uncommitted candidates saved. Without reopening, do not claim storage passed; a space comparison is not exhaustive document-persistence testing.

## 7. Diagnose control identity and host scope

For an unfound control, inspect current navigation; for system-looking keys, inspect field/switching; for absent saved text, inspect host-document identity. These are not one generic tablet incompatibility. Restore one condition and retain device/system/app state and feedback. External keyboards, window-system features and system-only gestures remain outside scope. Apple examples do not establish them for Jianlai. Use the nonsensitive card for help rather than private tables/accounts.

## 8. Restore A and deliver both control maps

Restore the original space state and identify everyday scheme/text. Deliver A/B maps, real entry and return results, including changed, unchanged and unchecked controls rather than two differently shaped pictures. Rebuild the map after host/system/layout changes. This is repeatable evidence for specified conditions, not physical-device certification of every iPad, window, split/floating feature or long-term performance. Unperformed conditions remain pending.

## Related guides and sources

[Three-line text boundaries](<https://allluckly.cn/en/guides/jianlai-three-line-draft-hard-break-soft-wrap/>), [Font-display scope](<https://allluckly.cn/en/guides/jianlai-font-size-label-candidate-comparison/>).

Checked on November 16, 2026: [Apple’s Finland lookup](<https://itunes.apple.com/lookup?id=6754281557&country=fi&entity=software%C3%97tamp=20261116>), cross-checked against China, lists Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. [Official store information and screenshots](<https://apps.apple.com/fi/app/id6754281557>) establish the input-language, layout and appearance scope; identify installed controls. Tasks use original nonsensitive samples. Storage and text selection depend on the host editor, without assuming unpublished keyboard tools. Keep expectations separate from observations; no completed physical-device or universal input-environment test is claimed.

[Apple: iPad onscreen typing (system-feature scope)](<https://support.apple.com/guide/ipad/type-with-the-onscreen-keyboard-ipad997da459/ipados>).

[Official Apple screenshot: keyboard layouts](<https://is1-ssl.mzstatic.com/image/thumb/PurpleSource211/v4/7c/74/9d/7c749d8e-919e-455e-f278-423cb12e045c/06-_U952e_U76d8_U5e03_U5c40-1206x2622.png/320x480bb.jpg>).

