# Changelog ## 0.1.12 (2026-11-14) ### Editor - `setSearch()` now resolves with `{ count, limited }`. `limited` is `true` when a very complex regular expression stopped early, so `count` covers only the matches found up to that point and a search bar can show it as partial. - An animated `scrollToLine()` now ends with the line at the top when soft wrap is on. Before, it stopped short in long documents with wrapped lines: going to line 1500 could end near line 743. - On iOS, `scrollToLine()` now stops a scroll that is still moving, such as a fling. Before, the fling could carry the view away from the line. - Calling `setText()` or `setInitialText()` during an animated `scrollToLine()` now leaves the new text at the top. Before, the animation kept going and scrolled the new text away. - On Android, dragging after a long press now extends the selection by whole words, with the same word boundaries as the long press. Before, the drag could stop inside a word the long press had selected. - On Android, an editor that unmounts while it is still highlighting no longer leaks the last highlighting result. - On Android, running out of memory during a call into the native code now reaches the app as a Java `OutOfMemoryError` instead of failing inside the native code. - The iOS code no longer uses `String(cString:)`, which recent Swift versions mark as deprecated, so app builds show fewer warnings. ## 0.1.11 (2026-11-13) ### Editor - The layout now runs in the same C++ core as the rest of the editor: the rows of each line, the gap rows under decorated lines, the scroll position, and the mapping between rows and the view. Each platform keeps its own text layout and drawing. On the iOS simulator, in the example app's Debug build, a draw of the 10,000-line benchmark file takes 10 to 15 percent less time than in 0.1.10. - When the visible lines at the end of the document lose rows, the view now moves up to the new end. Before, it showed blank space below the last line until the next scroll. - On iOS, an edit that removes the text under the scroll position now moves the scroll view too. Before, the text and the scroll view could sit at different offsets until the next scroll. - `onScroll` now fires when the editor moves the scroll position itself, for example when an edit removes text at the end of the document while the view is scrolled to the end. ## 0.1.10 (2026-11-13) ### Editor - The document, the selection, undo, auto-closing, indentation, cursor movement, bracket matching, decorations and search now run in the same C++ core as the highlighting, shared by Android and iOS. Each platform keeps its own view, text layout and keyboard handling. - Search regular expressions now run on PCRE2 on both platforms, instead of Java regular expressions on Android and `NSRegularExpression` on iOS. Most patterns match as before. When a pattern does not compile, `setSearch()` still rejects, and the message now comes from PCRE2 and ends with the position of the error in the pattern. A pattern that backtracks too much stops at PCRE2's match limit and keeps the matches found before that point. - Cursor movement and Backspace now find character boundaries with the Unicode 16.0 rules on every Android and iOS version. Before, they followed the Unicode version of the device, so an older device could split an emoji built from several code points. - On Android, word movement and auto-closing now treat U+0085 (next line) as whitespace, and no longer treat U+001C to U+001F as whitespace. iOS already did both. - `tabSize` is now kept between 1 and 64. Before, a negative value crashed the app when a line was indented. ## 0.1.9 (2026-11-11) ### Languages - The new `react-native-codepad-lang-xml` package has two languages: `xml` for XML documents such as Android layouts and SVG files, and `dtd` for a standalone DTD file. A `