From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gc66C-0007mn-C4
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:08:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gc667-0007ma-Jw
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:08:39 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gc667-0007mX-Cp
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:08:35 -0400
Received: from [199.80.85.4] (helo=library.beau.org)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gc667-0006mm-1f
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:08:35 -0400
Received: from mjolnir.library.beau.org (mjolnir.library.beau.org
	[199.80.85.12]) (authenticated bits=0)
	by library.beau.org (8.12.11.20060308/8.12.11) with ESMTP id
	k9NK8TYs001813
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <qemu-devel@nongnu.org>; Mon, 23 Oct 2006 15:08:29 -0500
Subject: Re: [Qemu-devel] RFC : disable SDL window close capability\n
From: John Morris <jmorris@beau.org>
In-Reply-To: <453C9D57.7020409@obs.univ-lyon1.fr>
References: <453C9D57.7020409@obs.univ-lyon1.fr>
Content-Type: text/plain
Message-Id: <1161634107.2976.3.camel@mjolnir>
Mime-Version: 1.0
Date: Mon, 23 Oct 2006 15:08:27 -0500
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Mon, 2006-10-23 at 05:45, Xavier Gnata wrote:
> Hi,
> I have been asked to disable the capability to close qemu by clicking on 
> the SDL window x icon.
> Any comments?

Totally disabling close is pretty drastic.  When the VM has went wrong
closing it is a valid option.  How about trapping close and throwing up
an "Are you sure?" dialog?  Give enough info to let a new user know that
clicking the "Yes" button might corrupt the VM's filesystem and cause
other permanent data loss.

-- 
John M.      http://www.beau.org/~jmorris     This post is 100% M$Free!
Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r