TOC incomplete - Page 2

KevinH · 06-20-2022, 04:29 PM

No, since creating an html toc is something best left until the end (all editing done). Also many people hand tweak an existing nav and do not want to fully regenerate them just to create a toc html copy.

So at best, I will change the menu entry and tooltip to be:

Create HTML Version from existing Table of Contents

or something along those lines.

KevinH · 06-21-2022, 09:46 AM

Actually that ToolTip is already there:

Code:

<action name="actionCreateHTMLTOC">
   <property name="text">
    <string>&amp;Create HTML Table Of Contents</string>
   </property>
   <property name="toolTip">
    <string>Create a new HTML file using the current TOC.</string>
   </property>
  </action>

So there really is no change to the tooltip needed.

Changed menu entry to be "Create HTML from Table of Contents" to clarify things even further.

theducks · 06-21-2022, 12:53 PM

Kevin
I would add 1 word to the tool tip
create/UPDATE
If there is a properly declared HTML TOC (semantics), it will replace the old one

JSWolf · 06-21-2022, 01:01 PM

Quote:

Originally Posted by theducks

Kevin
I would add 1 word to the tool tip
create/UPDATE
If there is a properly declared HTML TOC (semantics), it will replace the old one

Should that not be create/REPLACE?

theducks · 06-21-2022, 01:04 PM

Quote:

Originally Posted by JSWolf

Should that not be create/REPLACE?

could be either.
I was trying to make it clear that the existing on was being changed.

KevinH · 06-21-2022, 01:43 PM

The code already allows you to decide to overwrite an existing toc or not, so no replacement is forced.

Code:

        QString msg = tr("An existing HTML Table of Contents file has been found.");
        if (!ProceedToOverwrite(msg, tocResource->ShortPathName())) {
            tocResource = NULL;
        }
    }

DiapDealer · 06-21-2022, 02:32 PM

There really is nothing new under the sun here, Sigil-wise. The HTML ToC has always been rebuilt with the current content of the internal ToC (NCX for EPUB2 and NAV for EPUB3) for a long, long time.

Like Kevin, I don't really think there's much of anything that needs to be done. Tweaking the menu to indicate where the HTML ToC gets its data should be more than enough for those who didn't know. And the overwrite warning gives them opportunity to cancel should they so choose.

06-21-2022, 09:46 AM	#17
KevinH Sigil Developer Posts: 7,654 Karma: 5433388 Join Date: Nov 2009 Device: many	Actually that ToolTip is already there: Code: <action name="actionCreateHTMLTOC"> <property name="text"> <string>&Create HTML Table Of Contents</string> </property> <property name="toolTip"> <string>Create a new HTML file using the current TOC.</string> </property> </action> So there really is no change to the tooltip needed. Changed menu entry to be "Create HTML from Table of Contents" to clarify things even further. Last edited by KevinH; 06-21-2022 at 10:46 AM.

06-21-2022, 01:43 PM	#21
KevinH Sigil Developer Posts: 7,654 Karma: 5433388 Join Date: Nov 2009 Device: many	The code already allows you to decide to overwrite an existing toc or not, so no replacement is forced. Code: QString msg = tr("An existing HTML Table of Contents file has been found."); if (!ProceedToOverwrite(msg, tocResource->ShortPathName())) { tocResource = NULL; } }

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Incomplete book	Mysticfairy	General Discussions	24	09-21-2017 02:13 PM
Incomplete TOC Problem	Summerhillie	Conversion	3	02-21-2013 08:07 AM
incomplete pdf	rooeytoo	PDF	1	03-27-2012 06:58 AM
PDF incomplete	pepe1970	Recipes	1	06-24-2011 09:01 PM
The Incomplete Me	stevensavile	Self-Promotions by Authors and Publishers	0	04-23-2011 06:03 AM

06-20-2022, 04:29 PM	#16
KevinH Sigil Developer Posts: 7,654 Karma: 5433388 Join Date: Nov 2009 Device: many	No, since creating an html toc is something best left until the end (all editing done). Also many people hand tweak an existing nav and do not want to fully regenerate them just to create a toc html copy. So at best, I will change the menu entry and tooltip to be: Create HTML Version from existing Table of Contents or something along those lines.

06-21-2022, 12:53 PM	#18
theducks Well trained by Cats Posts: 29,817 Karma: 54830978 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	Kevin I would add 1 word to the tool tip create/UPDATE If there is a properly declared HTML TOC (semantics), it will replace the old one

06-21-2022, 02:32 PM	#22
DiapDealer Grand Sorcerer Posts: 27,553 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	There really is nothing new under the sun here, Sigil-wise. The HTML ToC has always been rebuilt with the current content of the internal ToC (NCX for EPUB2 and NAV for EPUB3) for a long, long time. Like Kevin, I don't really think there's much of anything that needs to be done. Tweaking the menu to indicate where the HTML ToC gets its data should be more than enough for those who didn't know. And the overwrite warning gives them opportunity to cancel should they so choose.