Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!decwrl!sgi!shinobu!odin!westworld.esd.sgi.com!erik
From: erik@westworld.esd.sgi.com (Erik Fortune)
Newsgroups: comp.windows.x
Subject: Re: xrooms question
Message-ID: <1990Aug23.000727.23493@odin.corp.sgi.com>
Date: 23 Aug 90 00:07:27 GMT
References: <9188@arctic.nprdc.arpa>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: erik@westworld.esd.sgi.com (Erik Fortune)
Distribution: usa
Organization: Silicon Graphics Inc.
Lines: 26

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.   If the event doesn't show up after a while, xrooms prints that
error message and continues.   0x1 is a state change, so it means that 
xrooms is either losing a property notify or it is unable to iconify
(or deiconify) a window.

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

If your connection is slow, the problem could be a lost event.   This
might cause xrooms to get confused about the state you want for your
application.   When the event finally does show up, xrooms can no
longer identify as the result of something that it did and instead
assumes the change was the result of something the user did.

If it happens once, you can probably safely ignore it or restart xrooms.
If you get this a lot, something else is going on.   Tell me a little
more about your environment, and maybe I can help track it down.

-- Erik
   (erik@sgi.com)