View Single Post
Old 05-31-2012, 03:06 PM   #330
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,238
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by kiwidude View Post
Yeah, there are two things here. The first is the bug in the Remove cover functionality, which is not removing the NCX entry, and also not doing the inline TOC.

The second is whether I should allow a user to select both options in the first place and interrupt the user. Or if behind the scenes I should just detect that the user had both selected and ignore the "Remove existing cover" option in that circumstance, which is probaby my preference.

The issue is that if I allow them to run in sequence (once the bugs are fixed), is that you will by doing so have lost both a link in your internal TOC and in your external TOC to the cover. Now since it was clearly your intent to put a cover into the epub, I see no use case where you intentionally want any existing pointers to the cover being lost?
If you don't want to go down the road of only allowing one of the two options checked, then I'd vote for the just ignoring the removing cover option.
JSWolf is offline   Reply With Quote