Re: FVWM: 2.2.0 and FvwmButtons unswallowing timing problem?

From: Jeff Wiegley <jwiegley_at_worldnet.att.net>
Date: Tue, 02 Mar 1999 02:11:18 +0000

Nope. That doesn't work for me either.

I still get multiple instances of xclocks and other things that
were swallowed and specified with (NoClose,UseOld).

Maybe I have too many things in my container to be unswallowed in time.

- Jeff

Brad Giaccio wrote:
>
> On Sun, Feb 28, 1999 at 10:36:00PM +0000, Jeff Wiegley wrote:
> > I've been trying to get the (UseOld,NoClose) to work witht the items in
> > my FvwmButtons module but it doesn't work as advertised.
> >
>
> Try using (NoClose,UseOld) I know that works for me although it should
> work either way we'll need to take a look at the parsing if this is the
> problem.
>
> --
> --- There are two kinds of knowledge, you either know the answer or
> you know where to find it
> -Kane, Johnson, and anonymous
> --
> Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
> To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
> message to majordomo_at_fvwm.org.
> To report problems, send mail to fvwm-owner_at_fvwm.org.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Mar 01 1999 - 20:12:35 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:02 BST