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: frame-resizing handles are no good (on Windows, at least) Date: Sun, 28 May 2006 19:36:03 -0700 Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1148870190 6481 80.91.229.2 (29 May 2006 02:36:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 29 May 2006 02:36:30 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 29 04:36:29 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FkXcJ-0000Yd-Ov for ged-emacs-devel@m.gmane.org; Mon, 29 May 2006 04:36:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FkXcJ-00078h-6c for ged-emacs-devel@m.gmane.org; Sun, 28 May 2006 22:36:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FkXc7-00078O-IT for emacs-devel@gnu.org; Sun, 28 May 2006 22:36:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FkXc5-00077n-3Y for emacs-devel@gnu.org; Sun, 28 May 2006 22:36:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FkXc4-00077k-WA for emacs-devel@gnu.org; Sun, 28 May 2006 22:36:13 -0400 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1FkXhY-00073s-4Q for emacs-devel@gnu.org; Sun, 28 May 2006 22:41:52 -0400 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k4T2aBhZ003003 for ; Sun, 28 May 2006 21:36:11 -0500 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-81-124.vpn.oracle.com [141.144.81.124]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k4T2aAj5000415 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 28 May 2006 20:36:10 -0600 Original-To: "Emacs-Devel" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE 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:55391 Archived-At: On Windows, I find that the frame resizing handles are far too small. When I try to grab a frame border, the double-headed arrow appears only when the mouse pointer is very precisely on the border line - so precisely that the double-headed pointer flickers on and off, without my even (seemingly) moving the mouse at all. That is, it changes back to the normal, single arrow of a standard buffer, which you see when the pointer is not over text. The tolerance isn't large enough, I suppose. And if I move the mouse to a border position where the double arrow appears, and leave it at that position, the double arrow reverts to the standard single arrow. IOW, the double arrow seems to be shown only when the mouse (pointer) is moving. Sometimes you can thus actually grab the border even though the double arrow is not showing at that position. This of course makes it difficult to use, because you cannot tell when you are on a sensitive spot. Frankly, trying to grab an Emacs 22 frame border reminds me of those hoax dialog boxes where you cannot click the button because it keeps moving out of the way - nice joke, but it gets old quickly. By contrast, when I run Emacs 20 on the same platform I have absolutely no such problem. I also have no such problem with other Windows applications (e.g. the Outlook mail frame in which I am typing this). Do others also experience this annoyance? If so, let's please fix it. Wrestling with this is a waste of time, besides being very annoying. I'd be surprised if this has not been reported before, if others see it too. I've never gotten around to reporting it myself, because I've assumed that it was a known problem that would be fixed in time - but now that the release is nearly baked that assumption appears faulty. Also, I don't think it's normal that as soon as you have actually grabbed the border successfully the pointer changes back to the normal, single arrow. It should stay as the double-headed arrow until you release the mouse button. I admit that I notice these problems more in my own setup, which uses multiple frames, than I do with just emacs -q and a frame or two (I don't notice the last problem mentioned with emacs -q, for instance). I doubt that my setup is doing something special that causes these problems, however - my code does nothing with the mouse pointer or the frame border. The same code also does not show these problems with Emacs 20. If no one else sees these problems, then I'll live with it, assuming that something in my setup is responsible. I don't have the time to try to track down the cause. If others see the same problems, then let's please fix them. Thx.