I just compiled a book from Scrivener (gush) to Kindle.
Usually Kindle books have all the chapter breaks denoted on the bar at the bootom of the screen, and you can jump quickly between them by using the left and right arrows (not the page turns, but the d-pad).
However, mine only denotes the three parts of the book, so there are only three huge sections which you can nevigate through for the whole thing. How do I make it so kindle recognizes the chapters? Everything looks wonderful, but you just cannot flip through the chapters.
I have it set up as:
Part (folder)
—Chapter (folder)
------Scene (document)
What do your settings look like in the Separators compile pane? By default the “Text and folder separator” should be set to “Section break” which is what will generate ToC entries. Going by the structural layout you posted, since chapters are folders as well you should be getting both parts and chapters in the ToC so long as every chapter has scene subdocuments (and if that is a problem you could add Section Breaks to the “Folder separator” setting, too.
Thanks, that’s what I had thought too. At one point I set every single thing set to “Section Break” and it divided it the same, except with section breaks, so that didn’t work.
But here are my settings:
Text separator: Custom
Folder separator: Section Break
Folder and text separator: Empty Line
Text and folder separator: Section Break
Also, my ToC shows all parts and chapters just fine, generated by the compiler, but it’s still only parts that have the little dots at the bottom that let you jump between them.
Got it. Looks like the dots are coming from the NCX data, which I had thought the Kindle doesn’t use, but it looks like it does use them for the dots, and it basically just takes the top level items in the NCX table of contents data for dot placement. Consequently, setting “Use flat list for navigable table of contents” pushes all NCX entries to the top level—thus turning them into dots. You can view how the NCX structure is generated using the Kindle Previewer software, which provides access to the NCX table via a button. When flat list is not set, the NCX provides a navigable tree based on your Binder outline structure.
Firstly, thank you so much for your help! That was the problem. The NCX menu was shown as an outline with the parts minimized, so the chapters weren’t getting navpoints. I clicked the checkbox, and voila, lots of dots! Thanks so much. I looked everywhere online, so helpful.