×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, 24 Nov 2004, Scott Klement wrote:
Does anyone know if there's a reason not to remove the calls to
XClearWindow? Obviously, anytime you clear the window and re-draw it,
you're going to get a flicker.
Ok, now I remember why I left XClearWindow() uncommented (notice the
commented code right next to it? I had been running with XClearWindow()
commented as well and fixed most of the problems). At this point (version
0.4.5) all of the problems that required a call to XClearWindow() should
be fixed except one: when switching from 132 column display to 80 column
the right window border has artifacts left in it from the previous 132
column screen. This is the problem I'm trying to fix.
I believe the artifacts are in the border of the smaller window, not in
the actual window itself. So I'm not sure I can draw there (though
XClearWindow() certainly does, so I ought to be able to). I might be able
to call XClearArea() with the coordinates of the far right edge of the
window to fix this when the window size changes.
James Rich
It's not the software that's free; it's you.
- billyskank on Groklaw
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
