There's little around that describes how XP actually manages the SysShadow
class (windows created using CS_DROPSHADOW style). Superficially it looks
like a fudge by Microsoft simply to add a dropdown shadow styled window and
the problem that I would like to resolve is to determine the ownership of
the SysShadow and how it is actually related to the associated parent
window.
Specifically, I've found that if you hide a window that does have a dropdown
shadow there's a problem caused by the SysShadow window being left unhidden.
There's been quite a few references to 'ghost' windows being left on screen.
If the SysShadow window is hidden also then it appears that showing the main
window again causes a new SysShadow class to be recreated and the old
SysShadow persists.
Andrew Jameson
