panel & FvwmPager problem:

[Toshio Kuratomi <badger prtr-13 ucsc edu>]

It would appear I was overly optimistic when I said the pager
could be put into the panel via FvwmButtons last -- When the panel
swallows FvwmButtons _on_startup_, the FvwmButtons module gets placed
in the panel, but the FvwmPager module inside gets left blank.

Removing that blank Swallowed App., starting a new FvwmPager and a new
FvwmButtons and swallowing that will work fine....

How does swallowing a module at startup differ from swallowing
it by selecting the appropriate menu item?

Also -- I just attempted to place xcb (XCutBuffer) into the panel --
The panel expanded to take up the whole screen (actually, it might have been
more than the whole screen.  My right and left edges were apparently the two
bars by which you can Explicitly hide and unhide the panel, but I couldn't see
any arrows on them.)  I think the panel allowed xcb to grow to take over the
entire inner area of the panel.

This may be related to my report that certain programs, when placed in the
panel, have a very small (perhaps one pixel) size.  Somehow these programs and
the panel are negotiating a resize when they are swallowed that is not far
from nice....

-Toshio
-- 
badger  \"The Difference between today and yesterday is not so much what has
@prtr-13 \ changed between then and now as what I hope to change by tomorrow."
.ucsc.edu  \~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

PGP signature