ProcessMonitor (Sysinternals) should be able to give me real-time access to filesystem, registry and process/thread activity. But I'd need to familiarize myself with it. Not sure about getting any of the signals that are firing, though.
I'm pretty sure it's probably somewhere in the deep magic being done with QFileSystemWatcher in ClipEditorModel.cpp and SearchEditorModel.cppp. There's a lot of hoops being jumped through to ensure cross-platform compatibility there, and I'm assuming the ini files' visibility, or accessibility is falling through some crack on Windows under rare conditions. Like the fileChanged signal is firing but the file cannot be found/read, so only the example entries get loaded/synced for that Sigil instance. Same with Saved Searches. Seems like there's countless reasons why a particular path added to QFileSystemWatcher might stop being monitored under different conditions (on different platforms) and need to be added again (after waiting to make sure the path exists after a write/copy).
Perhaps it's simply a race/timing issue with the other Sigil instances and normal Windows file-locking/access.
Last edited by DiapDealer; 09-22-2017 at 10:52 PM.
|