Write 16 bits (I think it came with Windows 3.11) reports now :
err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this.
This error message seems recent :
if (dc->w.flags & DC_DIRTY) ERR( "DC is dirty. Please report this.\n" );
This is really a strange message since a grep for this function gives
./graphics/x11drv/bitblt.c: if (dc->w.flags & DC_DIRTY) CLIPPING_UpdateGCRegion( dc
);
./graphics/x11drv/bitblt.c: if (dcDst->w.flags & DC_DIRTY) CLIPPING_UpdateGCRegion(
dcDst );
./graphics/x11drv/bitblt.c: if (dcSrc && (dcSrc->w.flags & DC_DIRTY))
CLIPPING_UpdateGCRegion( dcSrc );
./graphics/x11drv/bitblt.c: if (dcDst->w.flags & DC_DIRTY) CLIPPING_UpdateGCRegion(
dcDst );
./graphics/x11drv/bitblt.c: if (dcSrc && (dcSrc->w.flags & DC_DIRTY))
CLIPPING_UpdateGCRegion( dcSrc )
While I am at it, there is *another* strange problem with Word Viewer 97. It starts
correctly
now but the last line of the file I load (the readme) has a white background; if I
scrolls the text, the background is not erased so the new text overwrites the old.
Also if I switch to another app and back, the background is not erased. There
is no error message in this case, I'll try to get a trace but it will take time.
Gerard
