Wednesday December 22, 2021; 9:20 AM EST
- I've noticed people posting notes about the file-overwriting problem in their blogs, which of course is fine, but it would be good to cross-post those observations to a thread on the Support site. I don't know what the problem is, so any idea is worth considering. But let's not treat theories as bug reports.#
- For example, I read that people think it might be related to autosaving and switching tabs. The theory is that Drummer initiates an autosave on one tab, the user switches to another tab and in the process the file text is saved to the wrong file. I think this is so unlikely as to be impossible. The file saving happens inside a JavaScript closure for the tab. It couldn't get confused about what file it's writing to, the only file it knows about is the one it's managing. Think about it this way. I'm at the supermarket and use my credit card to pay for groceries. Then while the transaction is still being processed there, I go to the hardware store and buy a hammer. I use the same credit card. It couldn't accidently charge the hammer to Mookie Wilson's credit card. I simply don't have his credit card in my wallet. #
- But it was still worth considering for a bit of time. And I could put code in to verify a save after it happens. To see if the file it wrote is the same as the file you're editing. #
- BTW, here's the latest file-overwriting thread.#
- I also saw a feature request that we add a Save command to the File menu, and I assume also add an option to disable Autosave. If enough people really want that, I'll take a look at implementing it. #