View Single Post
Old 07-29-2019, 05:56 PM   #9
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,682
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
I'll take a peek. I am surprised that the physical location matters at all given how FolderKeeper actually works.
That was my thought as well.

I'm guessing that the error is somehow being triggered after the moving of the nav to it's new location and before the href to it gets updated in the opf. But that's not based on anything at all concrete: I haven't really jumped into it yet. We DID make a few tweaks to GetRelativePathToRoot() and few other functions in Resource.cpp recently didn't we?

Last edited by DiapDealer; 07-29-2019 at 06:00 PM.
DiapDealer is offline   Reply With Quote