Subject: Re: [9front] dangerous Exit menu item in sub-rio
Date: Thu, 18 Aug 2022 17:52:29 +0200 [thread overview]
Message-ID: <629C899644486EAE2F3FB802D33921EC@9lab.org> (raw)
Quoth Stanley Lieber <email@example.com>:
> what if the gray background is completely covered up?
Maybe I am doing something wrong but if the gray background
is completely covered I can not even bring the rio menu
that allows me to say `New`, `Delete`, etc.
Even if there is a way to bring up the menu when the
grey is covered up, isn't this similar to the case where
the window you want to `Delete` is hidden?
In that case you would bring the window to the front,
select `Delete`, and then select the window you just
brought to the front for deletion.
When the sub-rio you want to `Delete` isn't visible
because it is covered up, you need to make it visible,
select `Delete`, and then select the gray of the sub
That being said, I think there is agreement that the
process of Exit from a sub-rio should be a two step
process. Either select Exit and Confirm, or use the
semantics with `Delete` where the second step is selecting
the gray from the sub-rio as the target of the `Delete,
obviating the need for an additional menu entry.
My personal taste is for `Delete`, but the other options
is just as workable, no complaints.
> maybe exit could imitate delete and just require a second click (but this time, click anywhere and the current rio dies). we don’t have to call it a confirmation, we can pretend we’re a hunter targeting our prey. we could even borrow the skull and crossbones icon from mothra. maybe this would disturb the cognitive load just enough to be effective?
> > On Aug 18, 2022, at 9:51 AM, firstname.lastname@example.org wrote:
> > Quoth email@example.com:
> >> Why does `Delete` not apply to a sub-rio, i.e., why does selecting
> >> `Delete` and then clicking on the gray background of sub-rio not close
> >> the sub-rio? That way it would remain a two-step process and there
> >> is no need to add another menu option.
> > I think I like that.
next prev parent reply other threads:[~2022-08-18 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 5:34 Xiao-Yong Jin
2022-08-18 5:44 ` B. Atticus Grobe
2022-08-18 5:50 ` qwx
2022-08-18 9:17 ` Steve Simon
2022-08-18 10:48 ` Jacob Moody
2022-08-18 11:46 ` Jacob Moody
2022-08-18 11:56 ` qwx
2022-08-18 13:46 ` igor
2022-08-18 13:51 ` ori
2022-08-18 13:59 ` Stanley Lieber
2022-08-18 15:52 ` igor [this message]
2022-08-18 22:33 ` Stuart Morrow
2022-08-18 15:59 ` Jacob Moody
2022-08-18 16:18 ` Stanley Lieber
2022-08-18 16:22 ` Kurt H Maier
2022-08-18 16:57 ` Frank D. Engel, Jr.
2022-08-18 17:02 ` Stanley Lieber
2022-08-18 21:53 ` the lemons
2022-08-18 16:43 ` kvik
2022-08-18 22:30 ` Stuart Morrow
2022-08-18 15:16 ` qwx
2022-08-26 6:48 ` mkf9
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).