>>>>> Alan Wild writes:
A> Albrecht Kadlec wrote:
>
> Tim Phipps writes:
>
J> Also I don't understand why the examples of UseOld in the manual
J> all combine it with NoKill, when "NoKill" is the default anyway,
J> isn't it? Even with UseOld, is I restart fvwm2 a couple of
J> times, it seems to miss xload's, swisswatch regularly :-(
>
> I think Jarl meant NoClose to be used in conjunction with UseOld, in order
> to swallow old apps/unswallow them on exit.
>
> But this only works, when I do a "killmodule FvwmButtons" from FvwmTalk.
A> This feature (the UseOld/NoKill) option allows a user to start programs
A> from their .xsession file and then Swallow them into FvwmButtons. I
A> orignally suggested this idea to Jarl because I occasionally have to use
A> multiple window managers (HP VUE, CDE, et al.) and I only want to have
A> to start my clocks and xbiffs once. Using these attributes lets
A> FvwmButtons grab a window that was running previous to the start of
A> FvwmButtons and then Release the window when it closes.
consequently, at the restart of fvwm2 the new fvwmButtons should be able to
recapture the same window (process).
But the problem is that the window is lost.
The process still exists, but there is no mapping on any page.
so the new FvwmButton (in doubt) creates a new xclock/xbiff, every time I
restart.
Unswallowing only works correctly, if I do a killmodule FvwmButtons from
FvwmTalk.
albrecht
--
And the man in the mirror has sad eyes. -- Marillion
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Jun 13 1996 - 04:41:36 BST