[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bugreport: Next 100 button is grayed out incorrectly

From: Stefan Hett <stefan_at_egosoft.com>
Date: Tue, 29 Sep 2015 12:22:17 +0200

On 9/29/2015 9:19 AM, Lübbe Onken wrote:
> 2015-09-28 21:23 GMT+02:00 Stefan Küng <tortoisesvn_at_gmail.com
> <mailto:tortoisesvn_at_gmail.com>>:
> On 28.09.2015 15:52, Stefan Hett wrote:
> > Hi,
> >
> > tested with TSVN 1.9.2.
> >
> > Steps to reproduce:
> > 1. TSVN -> Merge... -> Next -> Show log
> > 2. LMB-click on the Message row to sort entries by message.
> >
> > Actual result:
> > The "Next 100" button is grayed-out
> >
> > Expected result:
> > The "Next 100" button stays active.
> log messages can only be fetched by revision.
> When you sort by anything other than the revisions, the button is
> disabled because it's not possible to fetch the next revisions
> sorted by
> e.g. messages.
> that's not a bug, that's by design.
> Would it make sense to leave the button active, fetch the next 100
> messages (by revision) and sort them in according to the currently
> selected column?
That's exactly the behavior which I'd assume. IMHO "Next 100" doesn't
certainly need to be the "next 100 items sorted by the column" I set.
It's quite obvious to me that "Next 100" always refers to the next 100
revisions (by revision number).
Even if I sort the current entries by any column, it's certainly not
showing the first 100 entries sorted by that column --- it's just
sorting what's currently already visible. So I've got really a hard time
following your argument from a user's point of view, Stefan. ;-)

But again, user interface design is a very subjective matter and it
wouldn't be the first time where I'm convinced that another behavior
doesn't make much sense which in the end everybody except myself agrees
to.... That's why user feedback (and usability tests in larger
companies) are so important. ;-)

On a side note: If you stick with the current behavior: Wouldn't it at
least make sense to enable the button even if entries are sorted by
"oldest revision first"? I mean in this case Next 100 is certainly still
correct even with ur argument, no?

Stefan Hett
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-29 12:22:29 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.