How the native writing surface, selection, undo, page capacity, recognition and handwriting pads behave.
Writing surface
Native PaperView/GPaper owns handwriting.
Calendar, search, settings and modal chrome never accept ink.
Pen contact and hover stay distinct, palm rejection stays on, ink stays within the A4 page, and page navigation is immediate.
Exclusions
A dropdown menu excludes the native writing surface for its whole lifetime, including nested options.
Window focus alone does not stop BOOX raw pen input.
Dismissing a menu restores the surface's current exclusions without changing tools or selections.
These exclusion rules also apply to dialog writing pads.
Selection
Ink selection uses g-paper's standard transform controls: eight resize handles (four corners, four edge midpoints) and a rotation handle centred above the top edge.
Dragging inside the box moves the selection.
Each completed transform gesture is its own undo entry.
When resize-handle touch areas overlap on a small selection, a central move target remains.
Each handle stays reachable at its own position, including on rotated and thin selections.
Undo
Limit
Value
Estimated history, shared across notebooks
8 MiB
Commands per writing session
200
Commands per page
50
When history is over budget, inactive notebooks are trimmed first, then their oldest commands.
Trimming never touches current ink or local-save state.
An edit larger than the whole budget is accepted, and clears that notebook's undo/redo so an older snapshot cannot overwrite it.
Edits after that can be undone again.
One eraser contact is one command.
A remote content change invalidates history from the previous generation.
Copy and replace confirmations say that Undo may be unavailable for large changes. They never promise recovery through Undo.
Page and note deletion keep their explicit permanent-deletion wording.
Page capacity
Limit
Value
Tiles per page
9
Ink per page tile
5 MiB
“Almost full” threshold
80%
ToDo handwriting tile
256 KiB
Writing into a tile that already holds 5 MiB of ink is refused.
The save-banner area then shows the static “This area is full” with Add page.
When a save leaves any tile of the page at 80% or more (read from the stored tile sizes, never by encoding while writing), the save-banner area shows the static “This area is almost full” with Add page.
“This area is almost full” stays until a save shows every tile below 80%, or the page changes.
Save errors, the memory pause and “This area is full” take priority over “This area is almost full”.
A ToDo's “Text” label reads “This area is almost full” once a check that encoded its ink finds it at 80%.
Erasing, Undo and moving ink out of the area stay available.
A page whose ink another device has not uploaded yet shows the static “Ink not synced yet” instead of a blank page.
Unreadable ink keeps its last good version and refuses edits. It is never shown as empty.
Failed local save
A failed local notebook save pauses new handwriting once the active pen contact ends. Hover does not delay the pause.
The visible ink and the native surface stay.
The save-error banner explains that changes remain in memory and offers Retry.
Retry covers every failed notebook save.
The pause continues during a retry and through Activity recreation.
The pause clears only when every failed notebook's accepted ink is saved locally.
Undo and Delete stay available, so a rejected oversized page can be corrected. The pause never traps content that Retry alone cannot save.
Pending contact and selection results stay accepted. The failure never discards them and never sends the user to subscription controls.
Memory pause
When retained notebook content exceeds its memory budget, new handwriting pauses at the next pen-up.
The save-banner area shows “Writing paused”, explains to save and change pages or undo, and offers Save.
Navigation and explicit recovery actions stay available. Accepted ink stays.
Writing resumes when retained content falls below the budget.
The pause never implies that a save failed or that unsaved ink is durable.
After sync
Sync's temporary input pause is always released, even when downloaded settings or a notebook reload fail.
Visible ink stays intact.
If no notebook can reopen, the static recovery screen offers Retry and Close.
New ink is accepted only once a notebook is available again.
Recognition
Recognition shows a static overlay inside the writing pad, disables native ink, and offers Cancel recognition.
On completion, the overlay disappears and the text-field label changes to Review text.
The text field stays three lines tall.
Progress and review never appear as new rows that move the pad, metadata or footer.
Recognition may reject ink that exceeds its SDK input budget, before making another sample copy.
A rejection shows its reason through the existing error feedback. All handwriting stays, typed text can still be saved, and edit recovery stays available.
Stored samples are never simplified or truncated to fit recognition.