From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27515 invoked by alias); 17 Dec 2012 18:38:39 -0000 Received: (qmail 27456 invoked by uid 22791); 17 Dec 2012 18:38:38 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mercury.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Dec 2012 18:38:30 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.1.102]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 17 Dec 2012 18:38:27 +0000 Message-ID: <50CF66A7.9060302@dronecode.org.uk> Date: Mon, 17 Dec 2012 18:38:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: heiko.bihr@secunet.com Subject: Re: Excess MotionNotify events to a minimized window in multiwindow mode References: <50C6318E.1020608@secunet.com> In-Reply-To: <50C6318E.1020608@secunet.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-12/txt/msg00011.txt.bz2 On 10/12/2012 19:01, Heiko Bihr wrote: > I think, there is a problem with mouse polling in multiwindow mode > (XWin.exe :0 -multiwindow) in Cygwin/X 1.13. > If a window gets maximized and then minimized, it will receive motion > notify events, whenever the user moves the mouse cursor over the screen. > > To reproduce the problem, please follow these steps: > > 1) start XWin.exe in -multiwindow mode > 2) start xev > 3) maximize xev window > 4) minimize xev window > 5) move mouse cursor around and watch xev output > > You will see lots of MotionNotify events from all over the screen. > X.org does not show this behaviour and I think, Cygwin/X should not either. I'm not sure I follow your reasoning. If you run 'xev -root', you can see that MotionNotify events are sent from everywhere. Is there some specific problem you are trying to fix? > The problem is caused by the WIN_POLLING_MOUSE_TIMER_ID, which doesn't > get stopped, when the user minimizes a window. > > I made a small patch against Cygwin/X 1.13.0-1 which will stop the > WIN_POLLING_MOUSE_TIMER_ID, whenever the user minimizes a window. If the > user changes the window's size again, and the timer was stopped, it will > be started again. > The patch introduces a new flag in s_pScreenPriv to remember the state > of the timer. Thanks for the patch. There are definitely some things wrong with the way that this mouse pointer polling timer works, I noticed during testing that is was possible sometimes to move the pointer out of an xeyes without starting the polling timer. I'm not sure this patch is right though: With this patch applied, if you have 2 xeyes running, minimizing the first one stops the second one from tracking the mouse pointer. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/