> Sigh. Do you use any of the window shading related styles?
>
> WindowShadeSteps
> WindowShadeScrolls or WindowShadeShrinks
> WindowShadeLazy or WindowShadeAlwaysLazy or WindowShadeBusy
>
> Or the obsolete WindowShadeAnimate command?
I don't use any of them. Until this Chrome thing came up I didn't
use WindowShade et al at all; I've added it to my setup only due
to Chrome.
> Can you post all your WindowShade related settings please? And
> what exactly is the command that triggers shading?
I'm triggering shading and unshading with:
AddToFunc Raise-Or-Move "I" Raise
+ "M" Move
+ "D" WindowShade
and then a titlebar mouse binding that invokes it:
Mouse 1 T N Raise-Or-Move
(as you might guess from the function name, the WindowShade on
doubleclick bit is a very recent addition.)
> Also, please try to grab the bottom border of the bad window, and
> drag it all the way up to the title bar (in opaque resize mode,
> not in wire frame mode). Stop resizing, then resize the window
> again to its original size.
This has no effect, but during the opaque resize things flicker
and I can occasionally see flashes of bits of window content.
> One more thing to try: Does maximizing and unmaximizing the window
> help? Or making it sticky and unsticky?
Maximizing and unmaximizing the window has no effect.
However, making it sticky and then unsticky is a winner; the moment
I make it sticky the window contents pop back (and they stay when I
unsticky it again, until I iconify it again). In addition while the
window is set sticky I can iconify it and then deiconify it and the
contents stay visible.
- cks
