From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
Date: Tue, 23 Mar 2004 15:49:47 -0800 [thread overview]
Message-ID: <dc80bfe04a37886c0f9bc47561d2a008@collyer.net> (raw)
In-Reply-To: <c9167f6cea8c715e0029b9f54cfe5a72@google.com>
I think there's another bug. Suppose you "cpu -c rio" and in the
inner rio (the one on the cpu server), create windows and hide one or
more of them. Then move the inner rio slightly (I dragged the border
a few pixels). I think that hiding and exposing the inner rio will
also trigger the bug. The inner rio then redraws its windows but now
it thinks the hidden windows are visible. If you select Move on
button 3, point the cursor where an invisible window was (but now you
can only see background) and click, you'll see a red border until you
release, then the hidden window will reappear.
Not only that, but if you now click button 3, the hidden window will
still be on the menu and can be selected, at which point it drops off
the menu.
If you often hide windows and have lots of overlap of windows, this
can lead to very mysterious behaviour.
next prev parent reply other threads:[~2004-03-23 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 18:53 andrey mirtchovski
2004-03-23 19:04 ` Russ Cox
2004-03-23 19:15 ` rog
2004-03-23 19:19 ` andrey mirtchovski
2004-03-23 19:30 ` rog
2004-03-23 19:45 ` rob pike, esq.
2004-03-23 23:49 ` Geoff Collyer [this message]
2004-03-24 4:35 ` rob pike, esq.
2004-03-24 7:54 ` Fco.J.Ballesteros
2004-03-23 19:50 ` rog
2004-03-23 19:51 ` rob pike, esq.
2004-03-23 19:47 ` rob pike, esq.
2004-03-23 20:09 ` boyd, rounin
2004-03-23 19:30 matt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc80bfe04a37886c0f9bc47561d2a008@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).