> I think (but am not sure) that we "rescan" far too much text, maybe
> even the whole block, in the text widgets when we redraw them, and
> that this accounts for the slowness.
>
> If we could contrive to only "rescan" the text that is visible (and
> some suitable boundary before/after the visible segment) I think it
> would be much faster - this is the way nedit was supposed to work,
> but we don't seem to have got this right...
What I remember from trying to debug Fl_Text_{Buffer,Display,Editor}
are a lot of recursive calls to [re]calculate line endings and visible
text limits, and it's this that makes it hard to understand the code.
If you add printf you get reams of almost useless output, and single
stepping in the debugger takes you through the same code all the time.
It's hard to work out where and when to set breakpoints :-(
I did find a repeatable example, so maybe I can resurrect something...
D.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
