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 u
On Wed, Mar 19, 2008 at 11:17 AM, Thomas Adam <[EMAIL PROTECTED]> wrote:
>
> But the window on $SOMEOTHERPAGEORDESK is unmapped, so of course it
> will come out blank, unless you switch to that page first.
Ok, so I would like FVWM to give me an option to force mapping windows
which are not on pa
On Wed, Mar 19, 2008 at 11:33 AM, Jesús Guerrero <[EMAIL PROTECTED]> wrote:
> 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 struct
On Wed, Mar 19, 2008 at 12:58 PM, Thomas Adam <[EMAIL PROTECTED]> wrote:
>
> You are -- it's nothing to do with FVWM at all.
So how can I prevent the windows from being unmapped? If there is no
solution in X, is there a way in FVWM that I can trigger a mapping
without forcing a virtual page chang
