Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965417AbbBCNeq (ORCPT ); Tue, 3 Feb 2015 08:34:46 -0500 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:42963 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753963AbbBCNep (ORCPT ); Tue, 3 Feb 2015 08:34:45 -0500 Date: Tue, 3 Feb 2015 13:34:32 +0000 From: One Thousand Gnomes To: Kay Sievers Cc: "Maciej W. Rozycki" , Takashi Iwai , Jens Axboe , Oliver Neukum , LKML Subject: Re: How to fix CDROM/DVD eject mess? Message-ID: <20150203133432.05f0bb0e@lxorguk.ukuu.org.uk> In-Reply-To: References: Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 23 > By working with people who spent a lot of time with the questions what > the default behavior of user interfaces should be. Buttons, especially > physical ones, need to give immediate feedback to the user. If they > don't give it it, people will look for something else to get what they > want. So spend a day in a location which isn't full of desktop users. In an environment where these are systems doing real world work you do not want to be having CD-ROMs eject because someone pushed the wrong button or because they bumped one. Locked media has its place. Your argument about feedback btw sounds rather like you've not thought it through. Users do want immediate feedback, but sticking a box on the UI that says "XYZ is currently using the CD-ROM, eject anyway" is immediate feedback too. Especially when XYZ is things like "The machine cutting tool" or "The telephone hold music system" Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/