Is there any way to pre index/cache books?

[goatdancer4000-sudo]

Im setting up an X4 with CrossInk on for my daughters friend. Its not a big issue but seeing as the hardware is slow, it takes a while to load, and then index a book before it can be read, especially if there are picture pages first and then text.
Is there any way other than me going through each individual book on the x4 to pre index before giving her the x4?

[RobertKats]

+1 for this. It seems like CrumBLE does something like this.
I would also pitch the idea for pre-caching just image so when you change the font or format it wont affect the image cache!

[uxjulia]

I think CrumBLE essentially creates an XTC-like experience when you "pre-bake" in the sense that all of your settings are pre-defined and you can't change them in the reader. That's the only way pre-caching would work, because the second you change your font, font-size, margins, line-height, etc. the cache is busted and the section needs to be re-built.

I did build into Inky the ability to generate the pre-cached pxc image file so image load times would be faster, I just haven't wired Crossink to actually use it yet. There is still a memory cost to register the fact the pre-cached image exists and to use it and all of that, I just haven't had the time to focus on that yet.

[RobertKats]

Ya 100% get that. TY for all the work you do!

There is still a memory cost to register the fact the pre-cached image exists

You mean within ram? I was thinking images could be pre-cached in the same way the "pre-bake" system works, when the renderer would find an image it first check the cache loc when the image would have been rendered to anyway.