On Sat, Dec 6, 2008 at 4:52 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> However, I should note that the scheme mentioned above implies, at > least in its naive version, that *all* text will be re-colorized > whenever any change is made. In contrast, a line-oriented scheme > might colorize only changed lines, and indeed highlightBlock appears > to be called only on those changed lines. Sounds like it would make editing quite slow with very large files. > > Presumably, QSyntaxHighlighter remembers the (optional) state info for > the start of those lines, and the (overridden) code that is charged > with coloring each line can get that state info. > > It may be possible to re-imagine what the state info means to get > these benefits. The first thought is to set the state of a line to > the starting location of the last previous pattern match. Alas, Why not use the state info as it's supposed to be done, i.e. just colorize the provided text, and save the "remaining" state to the object's state variable? Could the current code be tweaked to hold > I suspect the Qt people will be willing to fill this hole. It should > be easy to do, and it would open the door to non-line-oriented > coloring schemes. Note that Getting changes done to Qt will probably not a easy as for QScintilla, since it has to go through the whatever processes Nokia has in place for doing the chances. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
