On 27.10.2010, at 10:48, Duncan Gibson wrote:
>
>> 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...
Fl_Text_Input should work 100% for quite a while now. Please let me know if not.
Fl_Text_Editor has developed quite far, but still has some medium bugs in it. I
will restart my work on it in the next days.
- Matthias
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
