From: Stanley Lieber <email@example.com>
Subject: Re: [9front] dangerous Exit menu item in sub-rio
Date: Thu, 18 Aug 2022 13:02:25 -0400 [thread overview]
Message-ID: <B927E60A-BF54-40B4-A60D-15E1234EB1F8@stanleylieber.com> (raw)
config file for the exit button?
not for the menu, but the actual exit item itself.
> On Aug 18, 2022, at 12:58 PM, Frank D. Engel, Jr. <firstname.lastname@example.org> wrote:
> Why not move the confirmation to be first - so that the user needs to confirm that they even want the option to exit before it shows up in the menu?
> Or else have the option there but disabled unless a modifier key is held down on the keyboard (hold down shift or whatever to enable the exit item)?
>> On 8/18/22 12:22 PM, Kurt H Maier wrote:
>>> On Thu, Aug 18, 2022 at 09:59:40AM -0600, Jacob Moody wrote:
>>> On 8/18/22 07:59, Stanley Lieber wrote:
>>>> what if the gray background is completely covered up?
>>>> 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?
>>> This is exactly how it works now, following the latest commit made this morning.
>> Awful. Terrible. Clicking exit should result in a modal dialog
>> confirmation box, and upon confirmation should shitcan all running
>> processes in the subrio, black out the screen, and print "It Is Now Safe
>> To Turn Off Your Rio" in huge orange letters. The market has spoken.
next prev parent reply other threads:[~2022-08-18 17:03 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
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 [this message]
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).