States, languages and diagnostics

Jianlai inline mode: distinguish the toolbar-height recommendation of 40 from observed candidate space

In one ordinary text field, compare the original inline-mode value, the changed state and the actual toolbar height. The official image recommends a toolbar height of 40 after enabling. Keep recommendation, saved value and observed space separate rather than treat 40 as every device’s total keyboard height or a guaranteed improvement.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

In one ordinary text field, compare the original inline-mode value, the changed state and the actual toolbar height. The official image recommends a toolbar height of 40 after enabling. Keep recommendation, saved value and observed space separate rather than treat 40 as every device’s total keyboard height or a guaranteed improvement.

1. Record the original input area in one host

Create an ordinary note, confirm the visible keyboard is Jianlai and hold orientation, window state, theme, language and font fixed. Record which cursor, keys, candidates and toolbar actually appear without filling absent rows from promotional imagery. Enter 雨岸练习37, commit it and verify the characters and digits, preserving the draft. A field showing only the system keyboard needs setup or host investigation first. Limit the baseline to this window rather than import another app’s toolbar placement or an iPad floating state into the same ledger. Retain text and original layout settings so each later change has a recoverable reference.

2. Identify the switch and the object of the recommendation

The official high-resolution image shows Enable inline mode and recommends setting toolbar height to 40, with a path through keyboard settings and candidate-bar settings. The number names a specific setting, not measured pixels, total keyboard height or safe-area size. Locate identifiable equivalents in the installed version and record both original mode and toolbar value. Retain actual labels if they differ instead of tapping unknown screenshot coordinates. Without the entry, preserve version and stopping point; image reading can be completed but device switching cannot. A recommendation is a comparison condition, not an observed default.

3. Change only the mode and return to the same draft

After recording originals, change only inline mode and leave toolbar height untouched. Use the actual save/return flow, resummon Jianlai and observe. Record retained setting separately from actual changes around the keyboard and caret, without assuming the label proves a particular host composition mechanism. Note any old uncommitted content before starting at a distinguishable new position; do not splice old candidates into a screenshot of the new mode. Keep theme, size and host fixed. A system rearrangement is another condition rather than an effect automatically attributed to the switch. No visible difference is recordable evidence, not an immediate failure.

4. Check candidates and commitment with the same phrase

In an actually available Chinese state, enter the same phrase. Before commitment, observe composition, candidate placement and obstruction, then choose the correct result through real controls. After commitment verify 雨岸练习37 character by character. A briefly visible candidate is not committed text. Mark absent candidate types not applicable rather than invent codes, dictionaries or floating hints. The sample ledger is not an importable configuration or automatic in-app area-measurement tool. Preserve any confirmed round. For invisible candidates or failed commitment, record the stopping point rather than adjust many values until the original problem is lost.

manual columns: inline mode | toolbar value | visible candidates | committed text
practice text: 雨岸练习37
40 is a toolbar-setting recommendation, not a measured total keyboard height.

5. Make height 40 a separate one-setting comparison

With mode state established, locate toolbar height. If the actual control permits 40, apply the public recommendation while holding other conditions fixed. If already 40, do not deliberately disrupt it; record an unchanged value. Copy a unitless value as displayed without inventing percent, points or pixels, and do not confuse it with key-font percentages. Return to the same draft and repeat the phrase and area observation, noting obstruction, visible document and reachable controls. Forty is a recommended condition. If the original works better on this device, retain the comparison and restore it; comfort does not replace character correctness.

6. Separate overall area, toolbar and text sizes

Overall keyboard area, toolbar and candidate glyph size are different objects. Crowded text does not make every value a height. Record mode, toolbar value, visible candidate space, committed text and window conditions separately, with relative positions if useful and no unmeasured precise dimensions. A mode change may rearrange space, but the image guarantees no identical layout across hosts or orientations, and this is not a system-wide test. A different orientation needs a new condition after preserving the original, not direct subtraction of portrait and landscape. Apple’s custom-keyboard material helps distinguish host and keyboard responsibilities, not replace current observations.

7. Check entry and saved values before display problems

For no visible change, verify toolbar height rather than font size, saved value and the same keyboard/host. An affected composition area differs from an obstructed document; neither should become a generic input failure. For unreachable controls return to original values and ordinary input rather than clear dictionaries, uninstall or alter permissions. Restore one item per step so recovery is attributable. If the original mode does not restore the baseline, inspect a height value left behind. Invent no reload, cache-clearing or force-refresh menu. Deliver version, actual values and the repeatable short card when evidence remains limited.

8. Restore both originals and deliver the area map

Restore inline mode and toolbar height separately, return to the same note and verify input and final state. Restoring a switch does not also restore height, and recommended 40 does not supersede the recorded personal value. Deliver original, mode-only and height-recommendation rounds, marking unchanged values, unperformed stages and window differences with the phrase and real responses. Pass reopening only if performed. Findings concern this device, version and ordinary host, not every field, composition engine or device height. New fonts or orientation require renewed candidate/document checks rather than permanent reuse of one screenshot containing 40.

Fields and host boundaries; iPad input-area map.

Checked on 18 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store describes themes, backgrounds, fonts and multilingual input. Use controls actually present in the installed version; system editing and host processing are distinguished separately. These are repeatable instructions and paper expectations, not claims of completed device input, host compatibility or format-parser tests.

Method references: Official Apple keyboard-settings image; Apple custom-keyboard documentation.