Quote:
Originally Posted by DiapDealer
If that's what's happening; that's indeed not normal behavior. I don't see that on OS X.
I took the OP to mean that
1) Sigil is launched. Sigil opens to a "standard" new document.
2) The user then opens an existing epub using file-->open.
3) The user then has two sigil documents open: the initial new/empty document and the pre-existing epub.
If that's the case, that's indeed expected behavior. The newly opened pre-existing epub doesn't replace the empty epub that Sigil launched with like it does on Windows. This is how Sigil has always worked on OS X.
|
@
DiapDealer - I suspect you're probably right. In Windows if I start Sigil.exe I get the default empty file, if I then do a File->Open then, as you say, it replaces the default empty file.
But if I open the same file with Sigil from my file manager (say via Open With) then I get a second instance - i.e what Sigil does under OSX.
I always start with the data, by opening files with the program I want from within the context of my file manager, I have my own default empty file - so I never start Sigil from nothing.
I rarely use via File->Open in anything, so I tend to forget most people start programs and then find the data they want. Always seems back to front to me, it's like starting the barbecue and then deciding to have gazpacho soup and a salad
I guess it would be good to have Sigil consistent if that's easily doable.
BR