From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: mouse wheel events - why an extra ? Date: Thu, 7 Oct 2010 17:30:15 -0700 Message-ID: References: <87ocb5muv8.fsf@mail.jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1286497930 25102 80.91.229.12 (8 Oct 2010 00:32:10 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 8 Oct 2010 00:32:10 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Juri Linkov'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 08 02:32:09 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P40s9-00072I-A2 for ged-emacs-devel@m.gmane.org; Fri, 08 Oct 2010 02:32:08 +0200 Original-Received: from localhost ([127.0.0.1]:44180 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P40rR-0005iU-Nw for ged-emacs-devel@m.gmane.org; Thu, 07 Oct 2010 20:30:57 -0400 Original-Received: from [140.186.70.92] (port=54775 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P40rJ-0005hk-Bm for emacs-devel@gnu.org; Thu, 07 Oct 2010 20:30:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P40qw-0003cO-PW for emacs-devel@gnu.org; Thu, 07 Oct 2010 20:30:27 -0400 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]:34507) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P40qw-0003cJ-J2 for emacs-devel@gnu.org; Thu, 07 Oct 2010 20:30:26 -0400 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o980UMFW007616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Oct 2010 00:30:23 GMT Original-Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o97G4shb002308; Fri, 8 Oct 2010 00:30:21 GMT Original-Received: from abhmt014.oracle.com by acsmt354.oracle.com with ESMTP id 665535691286497809; Thu, 07 Oct 2010 17:30:09 -0700 Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 07 Oct 2010 17:30:09 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87ocb5muv8.fsf@mail.jurta.org> Thread-Index: ActmeiMIz/0b3Pj3RwmQjt170jeN2QAAsXgw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131449 Archived-At: > >> (defcustom foo-keys (list [nil (control wheel-up)] ; A > >> [(control wheel-up)]) ; B > >> "..." :type '(repeat sexp)) > > > > Sorry, I should have used the variables instead of > > constants, so you can try it on non-Windows as well: > > There is no wheel-up on non-Windows. Correct. Which is why I used the variables instead, in my followup mail that you replied to. You cut out that part of my mail, however - perhaps you did not see it. Here it is again: (defcustom foo-keys (list (vector nil (list 'control mouse-wheel-down-event)) ; A (vector (list 'control mouse-wheel-down-event))) ; B "..." :type '(repeat sexp)) That is not Windows-specific code, unlike what I sent in my first msg. BTW, I think now that the problem (bug, it seems) arises in particular when using a standalone minibuffer frame. My guess is that a frame-switch event or something like that might somehow be polluting the wheel event that gets returned, so that that event gets prepended to it somehow. With a standalone minibuffer frame this happens systematically, in the way I described previously. It is apparently not Windows-specific however. A user of my code who does not use a standalone minibuffer frame and does not use Windows said that he too saw the error a couple of times: "Some hours ago, I had an error message involving an mouse event starting with nil. I can't reproduce it. Never had it before, I think. [later] After 10 mins hardly trying to provoke it again, I had it one more time. I pressed C-h k and got the message " (translated from ) at that spot is undefined" with the mouse being over the echo area (of course, that's not the mb). It's not reproducible. Maybe it is related to switching frames with the window manager." On Windows the error message refers to " ". On his platform it refers to " ". He does not have a standalone minibuffer frame, which is why, I'm guessing, he does not see the error systematically. I don't have more info than that about this. Hopefully one of you will be able to enlighten us all wrt the mysterious that appears here as part of a mouse-wheel event but only in some circumstances. As I mentioned, the doc and Lisp code regarding the mouse wheel is not much help.