Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!emory!rsiatl!meo
From: meo@rsiatl.UUCP (Miles ONeal)
Newsgroups: comp.windows.x
Subject: Re: xrooms question
Message-ID: <3705@rsiatl.UUCP>
Date: 25 Aug 90 04:11:33 GMT
Organization: Systems & Software Solutions, Inc.
Lines: 23

erik@westworld.esd.sgi.com (Erik Fortune) writes:

|In article <9188@arctic.nprdc.arpa>, apple@nprdc.navy.mil (Jim Apple) writes:
|>	"Warning:          app Seashore waiting for a change (0x1)"

|This means that xrooms lost an event or that the window manager didn't do
|what xrooms asked it to.  Whenever xrooms tells an application to
|change state or to move, it looks for the corresponding events to come
|back....

|This happens most frequently with non-ICCM compliant window managers.
|Which window manager are you using?

I have had this problem occur when I started xrooms before my window
manager. Starting mwm first relegated it to the nearly never happens
category. I still get lots of BadWindow events on the server, but they
don't seem to affect anything.

BTW, could someone who has xrooms working with twm under R3 mention
in detail what you do to get it to work?

Thanks,
Miles