View Single Post
Old 05-22-2015, 10:12 AM   #9
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,849
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi,
Using a Mac (and testing with 0.8.6 since it is the most stable release so far) I can not recreate this at all. That said ... on a Mac you have only one instance of Sigil using different main Windows for each additional document opened. So you literally are always sharing the settings.

On Linux and Windows, you are actually running multiple instances of the main application, each trying to read/write the exact same settings files with each process having its own settings cache as well. Depending on exactly when the settings files are opened, written to, and closed. This may lead to issues without some sort of OS level file locking that can work across full processes.

I wonder if this is just a Windows issue? I have seen Qt file read and write operations return empty during simultaneous access when playing with Windows via my Parallels Virtual Machine. I assumed it was simply a virtual machine issue, now I am not so sure.

When I get a free moment, I will take a look at it unless user-none or DiapDealer beats me to it.

KevinH
KevinH is offline   Reply With Quote