[1015] in SIPB bug reports
Re: GRIPE about XRN 6.7 (for X11R4)
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sun Apr 15 05:48:44 1990
Date: Sun, 15 Apr 90 05:48:07 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: vinnie@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: vinnie@ATHENA.MIT.EDU's message of Sat, 10 Mar 90 09:34:25 -0500 <9003101434.AA03142@M14S-010-6.MIT.EDU>
A while back, you sent bug-sipb the following bug-report:
From: vinnie@ATHENA.MIT.EDU
Date: Sat, 10 Mar 90 09:34:25 -0500
Hi! Xrn is a great tool! I t really reduces the time I spend reading
netnews; thanks for installing it. I have noticed a couple of problems,
though:
1) When I'm selecting multiple articles by dragging with
the left mouse button depressed, it's hard (usually
impossible) to select just one more article. I usually get
an extra article on button release. When I'm trying to
scroll through the articles while selecting multiples (ie
holding the left mouse button while dragging the mouse off
the bottom of the list), the list scrolls much too fast and
I select too many articles.
2) When I'm selecting a list of articles and extending my
selection by pressing the right mouse button, I usually
(maybe always) extend the selection on both button down and
button up, thus extending the selection by two, not one.
3) When I've marked an article as "unread" and later press
"catch up" the article is no longer unread. "Rn" gets this
right - I want to keep the article unread, so I can read it
later.
I suspect 1 and 2 can be corrected by something in my Xresources,
if so, please tell me.
Thanks, Vinnie
First of all, I'm sorry it's taken so long for us to respond. I am
the main maintainer of xrn for the SIPB, and I've been very busy
recently.
Second, thank you for the compliment. I agree that it is a useful
interface to NetNews, and I've switched over to using it almost
completely instead of rrn. Previous releases of xrn had been very
difficult to use because they were constantly running out of memory,
but the last couple of versions have been quite satisfactory.
Unfortunately, I personally can't fix any of the problems you've
reported, and I also can't find any way to fix them in resources, so I
am going to forward your message back to the authors of xrn.
The first two problems you mention sound like boundary problems
related to the mouse being at the bottom of the article subject
window, and are also possibly caused by failure to treat button-down
and button-up events differently. The third problem is a bit more
complex, and may or may not get fixed, depending on whether or not the
author likes the current behavior :-).
In any case, thanks for reporting the problem.
--> Jonathan Kamens
Student Information Processing Board (SIPB) member
Project Athena Watchmaker and User Consultant
jik@Athena.MIT.EDU
