On Tue, 06 Oct 2009, Szak�ts Viktor wrote: > I know this. I need to clarify, by "messed up" I don't > mean the scrollbars and whatnot when using such big > buffer. Instead I mean that the displayed (by Harbour > app) _screen content_ is wrong. It looks like as if > (ctwin) windowing gets confused about current window, > so it's painting to the wrong one and returning size of > the wrong one. But I'll make some real tests later, > could be my app code.
It's possible that there is sth wrong in CTWIN though it should work correctly - at least I do not see any problems looking at the code. If you have some additional extensions then please check if you do not have some places which may cause coordinates casting to BYTE or which may calculate screen offset or index in screen buffer using [U]SHORT value. Try to reduce number of rows to 255 and check if it helps. Few years ago I made some tests with very large screen buffers in MS-Windows console and I've found some bugs in MS-Windows console code so it's possible that the problem is caused by exploiting them. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
