On Mon, Feb 27, 2017 at 11:39:18PM -0500 I heard the voice of [email protected], and lo! it spake thus: > > The problem is that despite the fact that the WSM was not beneath > pypanel, pypanel still has the WSM as part of the image inside of > pypanel.
My guess would be that pypanel put it there. Notice how it's dithered out; that would be how you'd fake up translucency. See the SHADE config param for pypanel, and the .py updateBackground() and the call to _ppshade() (in the .c file), which at a glance looks like it goes ahead and reads what's up on the screen, tints it down to act translucent, and then sets it as the background for the pypanel window. > I'm not certain if it is a bug in ctwm, pypanel, or perhaps an > underutilized WM hint that is causing this. I'd guess it's not _strictly_ a bug anywhere, just a clash of expectations. pypanel seems to expect the only thing under it is a background (which wouldn't move), not that you might have a window beneath it. If you started it with the WSM already moved out of the way, or did something else that caused it to redraw the whole panel, it'll presumably not be there. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
