From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Newsgroups: gmane.emacs.devel
Subject: Re: Gtk scrollbar: thumb too short
Date: Tue, 25 Mar 2003 14:55:46 -0500
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <200303251955.h2PJtkL0019666@rum.cs.yale.edu>
References: <20030325193739.ZGIN3924.fep01-svc.swip.net@gaffa.gaia.swipnet.se>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1048622380 18130 80.91.224.249 (25 Mar 2003 19:59:40 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Tue, 25 Mar 2003 19:59:40 +0000 (UTC)
Cc: =?ISO-8859-1?Q?Kai_Gro=DFjohann?= <kai.grossjohann@uni-duisburg.de>
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Mar 25 20:59:35 2003
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 18xuYY-0004aw-00
	for <emacs-devel@main.gmane.org>; Tue, 25 Mar 2003 20:57:58 +0100
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian))
	id 18xuZb-0000KP-00
	for <emacs-devel@quimby.gnus.org>; Tue, 25 Mar 2003 20:59:03 +0100
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18xuY0-00030I-09
	for emacs-devel@quimby.gnus.org; Tue, 25 Mar 2003 14:57:24 -0500
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18xuXB-0001ol-00
	for emacs-devel@gnu.org; Tue, 25 Mar 2003 14:56:33 -0500
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18xuWx-00014B-00
	for emacs-devel@gnu.org; Tue, 25 Mar 2003 14:56:21 -0500
Original-Received: from rum.cs.yale.edu ([128.36.229.169])
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.10.13)
	id 18xuWS-0000Mr-00
	for emacs-devel@gnu.org; Tue, 25 Mar 2003 14:55:48 -0500
Original-Received: from rum.cs.yale.edu (localhost [127.0.0.1])
	by rum.cs.yale.edu (8.12.8/8.12.8) with ESMTP id h2PJtkPe019668;
	Tue, 25 Mar 2003 14:55:46 -0500
Original-Received: (from monnier@localhost)
	by rum.cs.yale.edu (8.12.8/8.12.8/Submit) id h2PJtkL0019666;
	Tue, 25 Mar 2003 14:55:46 -0500
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
Original-To: "Jan D." <jan.h.d@swipnet.se>
Original-cc: emacs-devel@gnu.org
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Emacs development discussions. <emacs-devel.gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Post: <mailto:emacs-devel@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:12610
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:12610

> The current behaviour is the same as for Emacs compiled with Motif.
> To get the effect you want Emacs would have to write its own
> scroll bar.  The native scroll bar does indeed do what you want.

The Xaw3d scrollbar also suffers from the problem.  I have some
hacks to partly work around it in the code, and I have a patch
to Xaw3d which solves the problem (after all, Xaw does not suffer from
this problem), but I still haven't heard of any distrib using the patch.

> The advantages of being able to scroll so that the last line can be moved
> to the top can be questioned though.  It is not something other applications
> do.  Usually when the the last line is visible the thumb is at the bottom
> and you can not scroll so that the last line is moved to the top.
> But there is explicit code in Emacs for this behaviour so I figured
> that it had been decided some time ago.  It should perhaps be a
> settable customization?

Actually, this is also difficult to do.  What is the window-start
position that ensures that point-max is visible ?  The only
safe choice is when window-start == point-max.


	Stefan