This doesn’t directly relate to Twine, but it significantly affects how I use it. I am wondering if anyone’s come across this problem:
Local html files opened in Chrome are sometimes (and only sometimes) treated like file types that are open in other apps, where Windows will prevent you from deleting them (“This action can’t be completed because the file is open in Google Chrome.”).
Since Twine doesn’t tell you when it can’t overwrite a file, it leads me to situations where Chrome decides to not let it update the file, and I’m hitting refresh to see if some bug or issue is fixed and nothing has changed. It’s annoying.
The file won’t delete even if I close the tab the html file is open in and/or delete it manually in Windows Explorer. I have to shut down all the browser windows and wait a minute, then delete it.
Anyone had this? I don’t see why C would deny access to a file, it’s only supposed to read them, not write to them.