Right, sorry, missed that one. This might get complicated - while that might work for an in-memory model, it will be very complicated in the case of a large virtualized model.
An alternative might be to remove 'final' from replace(StyleResolver resolver, TextPos start, TextPos end, StyledInput input), or to allow a callback before the actual changes are made. I am not sure about the use case for this though. If you simply want to do a syntax or spelling check highlighter, you might need to keep a separate data structure that allows one to do, for example, a partial update, or to get the plain text from the model, or something else entirely. -andy From: Jurgen Doll <[email protected]> Date: Monday, November 3, 2025 at 00:36 To: Andy Goryachev <[email protected]> Subject: [External] : Re: RichTextArea Feedback Hi Andy > Did I miss anything? Please let me know. #2 Also, the RFE regarding ContentChange: This is a request to enhance ContentChange with an additional method: getPreviousSegments() Currently ContentChange reports only where something has changed. Using this one can determine the current state of the document, however determining what has actually changed is impossible. So having this extra information available would be helpful. I think this can easily be done in StyledTextModel where the previous segments can be obtained by extracting them from the freshly created UndoableChange object when calling fire?ChangeEvent(...) Thanks, regards Jurgen
