From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JTzUd-0002N1-AO
	for qemu-devel@nongnu.org; Tue, 26 Feb 2008 08:05:11 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JTzUa-0002Kr-Ru
	for qemu-devel@nongnu.org; Tue, 26 Feb 2008 08:05:10 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JTzUa-0002Kf-Ce
	for qemu-devel@nongnu.org; Tue, 26 Feb 2008 08:05:08 -0500
Received: from smtp02.citrix.com ([66.165.176.63])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <samuel.thibault@labri.fr>) id 1JTzUZ-0007gw-Mv
	for qemu-devel@nongnu.org; Tue, 26 Feb 2008 08:05:07 -0500
Date: Tue, 26 Feb 2008 13:04:23 +0000
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] SDL mouse events smoothness
Message-ID: <20080226130423.GL4430@implementation.uk.xensource.com>
References: <20080226125118.GI4430@implementation.uk.xensource.com>
	<alpine.LSU.1.00.0802261255210.17164@racer.site>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.LSU.1.00.0802261255210.17164@racer.site>
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: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org

Johannes Schindelin, le Tue 26 Feb 2008 12:57:25 +0000, a écrit :
> On Tue, 26 Feb 2008, Samuel Thibault wrote:
> 
> > I asked on the SDL mailing list, and they answered that qemu should 
> > indeed not use SDL_GetRelativeMouseState(), since that only provides the 
> > latest mouse position, not the position at the time of the event.
> 
> AFAIR this is done so that your guest system does not spend ages 
> processing mouse events from 10 minutes ago.  This could happen easily if 
> your guest is on high load.

Mmm, but these events currently _are_ sent to the guest...  Events could
be coalesced indeed (and an option provided to choose whether to do it
or not), but that's not currently the case.

> IOW I am not quite sure if I want the behaviour your patch provides, so if 
> that patch should be taken, there should be at least an option to turn 
> that behaviour off.

Well, at least compared to the current situation (a lot of undeeded
events pushed to the guest), my patch is just an improvement, because at
least these events are now useful.

Samuel