> One last bug that you are going to have to describe in greater detail - > "TextBuffer doesn't overwrite its previous contents" isn't doing it for > me based on the code fragment provided. > > Maybe you just need to force a redraw?
err, but i dont modify anything else to do with the text buffer or display, so that shouldnt be an issue; it's the same as a default text display. I'll give it a shot anyway. Err, that's not doing it. > Maybe the boxtype of the text display is wrong? (If you have set a FRAME > type rather than a BOX type the widget will not necessarily update its > contents correctly.) Again - nothing else is modified, so mine is the same as the default options you're running with. > FWIW, I wouldn't have used TextBuffer for this anyway, I think I'd have > used some less complex text widget. Even just using a straight TextDisplay still gives me the same issue. It's just not flushing the previous contents of the Display/Buffer before adding the new one. > (In fact, to be frank, I wouldn't have used fltk-2 for this at all, > since it is unsupported. I'd have used fltk-1.1 and output all the text > via an Fl_Browser, which is substantially simpler to use than a > textbuffer classes...) Heh, well, 2.0's never given me this sort of trouble before..... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
