MobileRead Forums - View Single Post - returning to same place in large table of contents

OttawaDeveloper · 07-11-2025, 01:35 PM

So in this long table of contents there is a section called blues. The song kansas city would be listed in that area of the table of contents.
The same song (same content page in the body) might also be listed in another section, for example favourites.
I could get to this song either way through the table of contents.
That said if i clicked the entry in the blues section, when returning to the table of contents it would be better to return to the place in the TOC where the blues songs are, not come to a different section, for example favourites, which also lists the same song but the context of how i got there is lost.
So there are multiple links in the TOC to a sing location in the body. When returning to the TOC could it be that it just finds any entry that matches rather than the actually keeping track of where we came from.

eg. and note this is a large TOC, over 1000 entries nested a bit like below. The TOC nesting/expanding tree thing is great to allow quick access to desired page rather than scroll over 1000's of pages.

TOC
---Blues
------Kansas City
------another blues song
---Favourites
------octopus garden
------Kansas city

I am not sure if i should report this here or in the github repo.

07-11-2025, 01:35 PM	#3
OttawaDeveloper Junior Member Posts: 2 Karma: 10 Join Date: Jul 2025 Device: kobo clara HD	So in this long table of contents there is a section called blues. The song kansas city would be listed in that area of the table of contents. The same song (same content page in the body) might also be listed in another section, for example favourites. I could get to this song either way through the table of contents. That said if i clicked the entry in the blues section, when returning to the table of contents it would be better to return to the place in the TOC where the blues songs are, not come to a different section, for example favourites, which also lists the same song but the context of how i got there is lost. So there are multiple links in the TOC to a sing location in the body. When returning to the TOC could it be that it just finds any entry that matches rather than the actually keeping track of where we came from. eg. and note this is a large TOC, over 1000 entries nested a bit like below. The TOC nesting/expanding tree thing is great to allow quick access to desired page rather than scroll over 1000's of pages. TOC ---Blues ------Kansas City ------another blues song ---Favourites ------octopus garden ------Kansas city I am not sure if i should report this here or in the github repo.