PuTTY semi-bug win-redraw
summary: Window redraw problems on Windows (white areas)
class: semi-bug: This might or might not be a bug, depending on your precise definition of what a bug is.
difficulty: taxing: Needs external things we don't have (standards, users etc)
priority: medium: This should be fixed one day.
present-in: 0.56 2005-01-13 0.58
We get occasional reports of failure to redraw parts of the PuTTY
terminal window, typically when another window is opaquely dragged
over the PuTTY window, leaving white areas on the window which can
usually be filled in by dragging another window over the PuTTY window
again. Two of us have managed to reproduce this ourselves with
Currently this looks like a Windows bug. We (JTN and OSD) can reproduce it with
apps other than PuTTY (for instance, in WordPad's menu bar). We're
assured that this probably isn't a function of the video card driver
(which isn't responsible for calculating what to redraw, just for
doing what it's told), but it may be a function of the Windows version
(all reports so far are on NT-series OSs, and my (JTN) attempts to
reproduce on 98SE didn't show anything).
(I (JTN) have a vague recollection about some misgivings and our
return value from window/dialog functions, or similar, compared to the
docs on MSDN, although this was years ago. I wonder if that could be
- 0.56, WinXP SP2, nVidia card
- 0.56?, WinXP pre-SP2, Matrox Millennium G550 (OSD)
- 2005-01-13, Win2K SP4, ATI RAGE 128 PRO II (JTN), 1.4GHz
Quite reproducible. Unable to get Notepad to exhibit the same
behaviour on similar timescales, so it seems PuTTY-specific.
(I can also trigger partial redraw failures on the configuration
dialog by the same method! -- the background
bizarrely. Also 0.56.)
Can also reproduce with WordPad menu bar, so probably not our
- 0.58 and previous; various video cards, XP Pro / 2000 Pro, many machines
Correlated with "East Asian Languages" in Region Options
20050319141100.GA68401@parodius.com et al
Audit trail for this semi-bug.
If you want to comment on this web site, see the
(last revision of this bug record was at 2008-02-10 14:42:39 +0000)