MobileRead Forums - View Single Post

davidfor · 12-26-2013, 04:17 AM

Thanks to Terisa and gwalden who are testing the annotations for the Kobo devices, it is very close to being releasable. But, both noticed something I didn't and now I can't work out if it is a bug in my code, the plugin or whether "it's not a bug, it's feature" applies.

The problem is when an annotation is changed on the device after they have been fetched. When the annotations are fetched again, there are two entries for the annotation. The first has the original text and the second has the new text. When I do another fetch, the original version of the annotation is removed.

So, I can't decide if this is a bug or not. I can see that what I describe might be deliberate. I don't think it is my code, as I am simply building the current list of annotations and passing it on to update the metadata.

I did have a quick look at the code that rebuilds the annotation text, but it didn't jump out at me as to whether what is happening is deliberate or not.

12-26-2013, 04:17 AM	#49
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Bug or feature? Thanks to Terisa and gwalden who are testing the annotations for the Kobo devices, it is very close to being releasable. But, both noticed something I didn't and now I can't work out if it is a bug in my code, the plugin or whether "it's not a bug, it's feature" applies. The problem is when an annotation is changed on the device after they have been fetched. When the annotations are fetched again, there are two entries for the annotation. The first has the original text and the second has the new text. When I do another fetch, the original version of the annotation is removed. So, I can't decide if this is a bug or not. I can see that what I describe might be deliberate. I don't think it is my code, as I am simply building the current list of annotations and passing it on to update the metadata. I did have a quick look at the code that rebuilds the annotation text, but it didn't jump out at me as to whether what is happening is deliberate or not.