View Single Post
Old 12-16-2014, 04:07 PM   #8
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,816
Karma: 6000000
Join Date: Nov 2009
Device: many
Hi BetterRed

Again I did not know that. On Mac OS X, double-clicking in the Finder (equivalent of Explorer) will generally open a new Window in the current app (all with a single process).

Can you recreate this Windows Crashing at all? Does it matter (crashingwise) if you use File->Open on Sigil versus launching another process? Which one crashes? Or is it both? It is really hard to believe that in this day and age, that one process can cause a second process to crash if not at a driver level or kernel level (ring 0)? So I am assuming the bug report was only for using File->Open in Sigil.

Thanks,

KevinH

Quote:
Originally Posted by BetterRed View Post
@KevinH - I think its Book View + Preview, Code View and Preview together seem to be OK, Book View by itself seems to be OK.

Aside : On Windows if you open EPUBs with Sigil (eg from file manager or calibre), you will get a new Sigil process for each EPUB opened, or if you start Sigil multiple times you will get multiple processes. It's only when you use File->Open that the current process is 'reused'.

BR
KevinH is offline   Reply With Quote