Navigation Buttons from chapter to chapter / book to book

[GregCM]

Bug

A whole book-search results in latency and potential crash upon scrolling through many lines of text.

Solution

Consider the BLB search results for Genesis, specifically the button layout below

where a single arrow goes forward or back one(1) chapter, and a double arrow goes forward or back one(1) book, alongside a dropdown of book options

Files in Question

• handler
• __init__

[GregCM]

Since latency in lengthy books will be an issue as long as tkinter or other ui is in use (and since whole-book searches are really less than ideal for all but a very few short books)... the best choice is to forego the double-arrow idea and replace it with a dynamic single arrow. Ergo, if I have in view a Verse, I want to show the next or previous verse with a click; if I have a chapter, show the next or previous chapter. The result of this structural change will be that any whole-book searches, ie "Genesis" will only return the first chapter, but will be much easier to navigate through (sidenote: it may still be valuable to save an entire book, but this doesn't have to be TextWidget dependen).

Additional Feature Idea: If I have in view a Verse, it would be much less anti-climactic to show the previous and next verses before the actual search item. Navigating rightwards will "scroll" to the next visible verse, rid the leading context verse, and add a the next trailing context verse.

This is especially valuable in a single result search, where there's nothing to look at but one verse, maybe 10 words long, no other options, and only a search bar to direct my thoughts.

• Chapters
  • Up/Down within a book
  • Up to previous book (final chapter)
  • Down to next book (first chapter)
• Verses
  • Up/Down within a chapter
  • Up to previous chapter/book (final verse)
  • Down to next chapter/book (first verse)