View Single Post
Old 11-14-2019, 11:42 AM   #25
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,873
Karma: 6120478
Join Date: Nov 2009
Device: many
Just tried it with F&R open with no problems whatsoever. I go through the exact sequence of events described here:

1. Fire up Sigil with an empty epub
2. Highlight Section0001.xhtml in BookBrowser and invoke Save As via the context menu
3. The file save dialog comes up and I save the file under its default name (or a new name)
4. The save file dialog goes away
5. I close the Sigil window which does not exit the app, it is still running and can be clicked
6. I drag a new epub to the Sigil icon in the doc (or select it and use the File menu item to load a new epub
7. The new epub loads but no old file save dialog anyplace! I even move the new Window around to be sure it is not hidden underneath.

I repeated this 10 times, and I am simply never getting an old file save dialog to come back in any way.

So this is specific to your machines in some way. I am not even sure where to put debug statements to help track down why this is happening on your machine.

If neither of you have added software that adds kernel extensions, then I am not sure what is going so.

Would you both please try the following:

Save all your work.
Restart your mac and hold down the Shift key immediately after you hear the initial start-up tone.
Then fire up Sigil and try your test one again after a clean "safe" reboot.

Does the problem still happen?

KevinH
KevinH is offline   Reply With Quote