FVWM: backing windows off currentpage

[jieryn]

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.

Thanks in advance,
-jesse

Re: FVWM: backing windows off currentpage

[jieryn]

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 page. Perhaps I used the wrong language in the
original post, but that's what I thought I was asking for originally.
:-)

-jesse

Re: FVWM: backing windows off currentpage

[jieryn]

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 structs
>  to rescue bitmaps. This is an X thing, not an fvwm ones. Or maybe I
>  misunderstood something.

Yah, that makes sense. I thought that FVWM was doing something in its
virtual page / desk code that would identify windows as "off screen"
and therefore eligible for memory reclaimation. So, if we could stop
marking windows as being off screen and/or triggering X to unmap them
when the user changes pages / desks, that would be ideal!

Thoughts?
-jesse

Re: FVWM: backing windows off currentpage

[jieryn]

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 change?

-jesse