View Single Post
Old 04-08-2021, 10:03 PM   #21
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by KevinH View Post
I am curious ... is the fast time for calibre to merge, is that done with Preview actively showing the file being merged into, or a different file, or is that with the Preview updating message showing?
I made sure to keep the "Chapter1.html" tab open as the active tab.

I just tested Calibre again, and it looks like it does this:

1. Preview is generated.

2. Keep "Chapter1.html" open as the active tab.

3. Shift-click + highlight all chapter files.

Right-Click > "Merge selected text files"

Select Chapter1.html bullet.

4. It looks like preview window still keeps the old Chapter1 preview cache (?) displaying there.

5. The instant you click within Code View, the preview window kicks into "Loading preview, please wait..." and takes ~6 seconds to generate a new one.

But as I said, the entire time, you're able to edit code, open up menus, etc. etc. all at full-speed.

Sigil, at that point, every single thing you click on or do became a slog.

Also, as I was typing my post above (~30 mins), I noticed when I clicked back into the merged Sigil window, the entire window re-froze up and went back to "Not Responding" for maybe ~15 seconds. (Preview not open.)

Quote:
Originally Posted by KevinH View Post
A second thread just to load Preview is doable but seems like overkill. But waiting for Preview to load could be handled more asynchronously, as long as it does not interfere with syncing from Preview back to CodeView.

I assume calibre is using multiple threads to handle the merging as well. That might make some sense to look into.

Last edited by Tex2002ans; 04-08-2021 at 11:31 PM.
Tex2002ans is offline   Reply With Quote