DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2808
Version: 1.3.0


Yes, that's what I've been looking at too..

I was thinking there's a bug in the straddle code, since the corruption
seems to appear at the buffer size boundary (131072, or 128*1024).

Indeed the 131072 buffer is not an even multiple of the 100 byte
line buffer, so that's probably triggering it.

I'm trying to add comments to that code so that it's easier to read,
so the actual bug can be identified and fixed.

I think there might be some room for optimization in that function
too, to avoid all the utf8 encode/decode stuff in cases where the
ascii is detected. (Right now it seems to always do the utf8decode
and encode calls, even for ascii input data, which seems a waste).

Another workaround that would make large files load quicker
would be to just make your own file load routine that loads
the data into a char* buffer a chunk at a time, and append this
to the widget a chunk at a time.


Link: http://www.fltk.org/str.php?L2808
Version: 1.3.0

_______________________________________________
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to