Quote:
Originally Posted by chaley
Sort-of depends on what you mean by significant. 
The problem I fixed related to on-device matching. The problem was that a book on the device could match multiple books in the library, which makes no sense. Kovid and I worked out a scheme where the books will match the one-closest book in the library. This is good.
While testing this fix, I discovered that adding and deleting books in the library and on the device did not update on-device correctly. In some cases it was totally wrong. I attempted to fix that. Unfortunately, I broke some other things. That is the way of software -- changing one character 'here' can completely break what happens 'there'. Sigh.
As it turns out, the actual problem was introduced a few releases ago as part of redoing parts of the content server. Seems that no one noticed. Not surprising, given the corners of calibre I was playing in. My problem was assuming that those changes worked *there*, so I could reproduce them *here*. The code-daemons answered quickly -- "no, you can't".
(It is late and I am rambling.  ) |
Thanks for the explanation. I actually know that "process" of accidentally breaking things that cannot possibly be broken by the code you're changing right now... Though far from being a programmer, I've written some code myself, and, at the moment, I'm trying to learn Python. I really need to take a weekend off and just absorb the whole tutorial in one go, I think...
It's late here as well, can you tell?