![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Mar. 1st, 2018 08:12 amOkay, that's two out of the last three months that a software gremlin has eaten my log file just as I was about to copy it over to this computer and write up my fiction log post. There's definitely something up. I just wish I knew which of the various moving parts it's likely to be. Is it the tablet? This computer? Something about the process of copying it from one to the other? Something I did last month when I created the file and have forgotten about since? Argh.
Edit: But now it's back. Or isn't, depending on which app I'm in, and at least one is reporting that both the good version and the eated version exist simultaneously. *uses that app to make back-up copies of the good version*
Edit: Aha! It's not that the file was eated, it's that the app has been saving the updates in the wrong folder all month, cunningly disguised by the fact that it's not very forthcoming about which folder it's using. And it's an internal app data folder, or something, whose contents don't show up in a file search, which is why when I did a file search in case the file just wasn't where I thought it was I didn't find anything. So, in fact, the good version and the eated version do exist simultaneously, but it's only the badly designed app interface that makes them look like they're existing simultaneously in the same location (and the eated version isn't actually eated, it just hasn't been updated all month).
Edit: I think I've pinned down the location of the gremlin. If I open a text file using the Open File dialog box in the text editor app, changes are saved to the same file -- but if I open the text file from inside the file explorer app which I use to copy the log file between computers, the text editor app creates a new file of the same name in its private file space, and saves the changes there. (And if I subsequently reopen the file using the Recent Files dialog box, it will continue to be whichever file, and it won't be obvious which, because the Recent Files dialog box only lists file names, not which folders they're in.)
Edit: But now it's back. Or isn't, depending on which app I'm in, and at least one is reporting that both the good version and the eated version exist simultaneously. *uses that app to make back-up copies of the good version*
Edit: Aha! It's not that the file was eated, it's that the app has been saving the updates in the wrong folder all month, cunningly disguised by the fact that it's not very forthcoming about which folder it's using. And it's an internal app data folder, or something, whose contents don't show up in a file search, which is why when I did a file search in case the file just wasn't where I thought it was I didn't find anything. So, in fact, the good version and the eated version do exist simultaneously, but it's only the badly designed app interface that makes them look like they're existing simultaneously in the same location (and the eated version isn't actually eated, it just hasn't been updated all month).
Edit: I think I've pinned down the location of the gremlin. If I open a text file using the Open File dialog box in the text editor app, changes are saved to the same file -- but if I open the text file from inside the file explorer app which I use to copy the log file between computers, the text editor app creates a new file of the same name in its private file space, and saves the changes there. (And if I subsequently reopen the file using the Recent Files dialog box, it will continue to be whichever file, and it won't be obvious which, because the Recent Files dialog box only lists file names, not which folders they're in.)
