Sharing violation on script reloads

I use Dropbox to sync my MUSHclient directory and when I edit my script file (and it autoreloads) I end up with a race condition and sometimes MUSHclient gives me a:



If MUSHclient "wins" the race and the error pops up then forcing a reload (CTRL+SHIFT+r) fails to reload the script file and, from what I can tell, any triggers that call a script function silently fail. i.e. you don't get that black on red called-a-failed-trigger notice. The whole race condition makes it tough to debug from the user end.

If you manually go into the World Properties->Script and do basically anything relating to the script file it will reload normally but the hotkey combo itself doesn't work.

It's completely work-around-able, but a bug nonetheless.

I dug around git for a while looking for a solution but I'm a hardware guy. Following complex software code is not my forte.

Edit: Ok, from what I can tell, there's some master-suspend-on-double-plus-bad-error that halts interpretation across the board which prevents the hotkey from even bothering (exact text below). It's not eliminated by anything in the script tab, it's only eliminated by something that rechecks the files. Even opening "Browse" and canceling it results in a sucessful relod.

I wouldn't be auto-reloading from a remote server, personally.

I was talking today to someone that said how wonderful it was to have stuff "in the Cloud". Wonderful maybe, but it comes with drawbacks.

TANSTAAFL

I wouldn't do that, either; this is a local copy

MUSHclient is hitting purely local file lock and halting any attempt to reload until it thinks that I've made a change to the actual file.

Except.. There are a number of cases where having such cloud services active on a system can cause issues. Sounds to me like the cloud service is "locking" the file itself, until it can get around to updating its cloud copy, and the result is causing Mushclient to try to reload what, according to the file system, at that moment, is "unavailable". The moment I read that you where ghosting the files to a cloud service I thought, "Hmm.." Its seems to be, literally, the only factor that exists in your case, which doesn't in everyone else out there, who, I am sure, are using auto-reload all the time.

Not sure how to fix it, unless there is some check that can be added to Mushclient to check the state of the file, before trying to reload it. No idea how that works though.