3 small points

[SteveB]

Actually 3 small things. NONE of these is any big deal whatsoever but I would like to just mention:

(1) In Ebook editor, Tools - Beautify All files used to give an OK prompt at the end but since 2 or 3 versions no longer does, it finishes silently. I much preferred the previous method since sometimes the process is quite long.

(2) The new Book Editor icon is very nice, but in the taskbar (windows 10) I still see the old icon (or do I need to delete iconcache or whatever?)

(3) Tools - Remove unused css rules has an option "remove unused class attributes". But in fact, "remove unused class attributes" is completely independent of "remove unused css rules" and shouldn't be a sub-option. It's no big deal but definitely illogical. I quite often want to remove unused classes without removing unused rules (e.g. when fixing up merged books) and have to work around this.

Cheers :-)

[Kovid Goyal (kovid)]

On Thu, Nov 03, 2016 at 07:37:18PM -0000, SteveB wrote:
> Public bug reported:
>
> Actually 3 small things. NONE of these is any big deal whatsoever but I
> would like to just mention:
>
> (1) In Ebook editor, Tools - Beautify All files used to give an OK
> prompt at the end but since 2 or 3 versions no longer does, it finishes
> silently. I much preferred the previous method since sometimes the
> process is quite long.

It has never had a prompt. And it sets the mouse cursor to busy. I can
have it also flash the taskbar icon when done.

>
> (2) The new Book Editor icon is very nice, but in the taskbar (windows
> 10) I still see the old icon (or do I need to delete iconcache or
> whatever?)

The taskbar icon comes from inside the exe file, and cannot be overridden
using the normal calibre icon theming system, so I decided to leave it
alone, since users cannot easily reset it to the old icon.
Perhaps I'll revisit changing it in the future. You can always manually
override icons for programs in windows, a bit of googling should get you
instructions on how.

>
> (3) Tools - Remove unused css rules has an option "remove unused class
> attributes". But in fact, "remove unused class attributes" is completely
> independent of "remove unused css rules" and shouldn't be a sub-option.
> It's no big deal but definitely illogical. I quite often want to remove
> unused classes without removing unused rules (e.g. when fixing up merged
> books) and have to work around this.

Yeah, but the code for implementing them has a lot in common, which
makes separating them rather more work that I am interested in putting
in. Patches are welcome.

[Kovid Goyal (kovid)]

Fixed in branch master. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased