Quote:
Originally Posted by TechniSol
To be expected since it still thinks it's in the previous chapter. Somebody just forgot to increment a common pointer or variable somewhere.
When you consider how many variables are being accounted for, and used in different operations and dialogs I can see how it'd be easy to miss without testing routines based on variable dependencies every time you changed a module.
|
It's actually used in a few more places. As well as the TOC display and navigation bar, it is used in the annotations system. These are all stored relative to that last chapter selected. In the annotations list, the annotations will be listed under the wrong chapters. The current reading position is also stored relative to that chapter. I've seen a few comments elsewhere that epubs are reopening a pages or two off. I suspect that it is because the relative position over the whole book isn't as accurate as if it was to the current chapter.
As to development, I've worked solo, in small teams and in big teams. The processes in each situation are what saves you (plus knowing when to ignore them and occasionally walking around with a big stick). And as Terisa said, automatic test-cases help a lot.