OK - my suggestion is to make this much, much, simpler. Have a preference for whether styling is done or not. Have the preference wizard point out if the machine seems slow (it already does this, neh?) and explain that turning off auto-styling might be a good idea.
Of course, making the styler much faster would also assist in making this better.
On 2023-08-19, at 5:49 AM, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Context: At the moment, PluggableTextMorph runs the text styler immediately (#updateStyleNow) or in the background (#updateStyle) depending on the trigger:
- Immediately: The user accepts a text; we change the text programmatically (e.g., when opening a browser or selecting a different method). However, the text must be shorter than 4096 characters for this.
- In the background: All other triggers: the user types or cancels; we change the style programmatically (e.g., after a preference change); accepting or changing a text longer than 4095 characters.*
So, this strategy tries to balance maintaining a responsive UI for longer texts (especially during typing) and minimizing flickering.
Problem: There are situations where we still have too much flickering.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: RBT: Rewind and Break Tape