Why is the more option given when there are no additional entries?

MJ. Smith · 2025-01-30T22:04:38+00:00

There was an error rendering this rich post.

MJ. Smith

Note the More brings up the message "no more passages to list"

Find more posts tagged with

Bug

Desktop App

Accepted answers

All comments

Ronny Woods (Faithlife)

Hi @MJ. Smith — the short answer here is, we don't know if there are more results until we try to get the next page. The nature of the underlying technology (or rather, our approach to using that technology) prevents us from knowing upfront how many results there will be (I think you may have made a separate post about the lack of result counts in Smart Bible search … this also explains why we don't / can't show the total result count).

We could of course eagerly fetch more pages of results before deciding whether to display a more button, but there's cost associated with each page of results we fetch—cost that's significant enough that it doesn't make sense to get the results unless/until you (the user) specifically requests them.

MJ. Smith

@Ronny Woods (Faithlife)

Good answer unless one tries to "solve the problem" i.e. why not gather one more answer than you are displaying i.e say you are displaying 50 responses: the first time you ask for 51 responses and display 50 —> if there is no 51st response waiting, you know you are done; second time request 50 responses, display the 51st from the first query and 1-49 of the second query … an so on… I don't think the addition of 1 additional response one time has a significant cost AND it saves the cost of a separate query to tell you there are no more.

Mark Barnes (Logos)

From a UI perspective, hiding one of the results we get to ensure that clicking "more" always displays at least one result is an interesting idea.