On 19/03/2008, Jesús Guerrero <[EMAIL PROTECTED]> wrote: > On Wed, 19 Mar 2008 15:17:30 +0000 > > "Thomas Adam" <[EMAIL PROTECTED]> wrote: > > > > On 19/03/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > It seems that FVWM does not back windows which are on some > > > non-CurrentPage. If I run xwd -id $someWindowNotOnCurrentPage the > > > image comes out as completely black. I would request that FVWM exposes > > > a configuration option that would keep windows backed in memory such > > > that programs like xwd produce a usuable result even when they aren't > > > on the current page. Perhaps it would be nice to have this feature be > > > both a global tri-state (off, on for current desk, on for all desks), > > > as well as a per-window option toggleable via Style or Pick type > > > actions. > > > > But the window on $SOMEOTHERPAGEORDESK is unmapped, so of course it > > will come out blank, unless you switch to that page first. > > > > -- Thomas Adam > > > > I think he means caching a bitmap of that window from the last time > that it was mapped, until it's mapped again. However, if fvwm did that, > then it's an fvwm thing, and I don't think that xwd looks into fvwm structs > to rescue bitmaps. This is an X thing, not an fvwm ones. Or maybe I > misunderstood something.
You are -- it's nothing to do with FVWM at all. -- Thomas Adam
