View Single Post
Old 06-19-2025, 12:36 PM   #56
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by KevinH View Post
You should not use the same approach to grey out the epub3 Tools menu as it is not tied at all to CodeView. Those tools should be available at all times on epub3.

In addition, all of that menu and its contents are protected against being run on epub2 (will warn you and not do anything) and they have been there from Sigil 0.9x betas and are required tools for epub3 users to get a working epub, not optional like the Accessibility Insert Roles ...

So no change there. That menu will stay enabled I think.
But we could disable its submenu contents.

I have taken a shot at disabling all the epub3 Tools submenu items (greyed out) on epub2 just like BeckyEbook but did not tie it to CodeView. Instead it happens in UpdateUiWithCurrentFile which is called after every epub load and when creating empty epubs.

I have pushed this to master on my repo.

Last edited by KevinH; 06-19-2025 at 12:41 PM.
KevinH is offline   Reply With Quote