Within the project folder, the underlying RTF file representing the snapshot wonât use that name anyway but a random UUID, so itâs not going to make much difference for the external comparison tool.
So I really would have to find one by one and manually go through all of the changes? There is no way of doing that (at least partially) automatically?
I donât follow what youâre saying here. From what I understood of your description earlier, you have two separate main project windows (that can display binder, editor, and inspector) purportedly showing the same project, and I gathered that changing the display in one did not affect the appearance of the other.
Yes, all of this is correct. A single (properly open / running) project can have more than one window. So one can open a doc, folder in a new window (instead of opening it in the main window). One can open, so to say (limited by the computer or else), as many windows from a single project as one like to, I guess. So there is one project or two of the five projects with two instances each having more windows open than the two windows showing the two instances (that can display binder, editor, and inspector each) of a single project. But I just would assume, these other windows additionally open to the two windows showing the two instances of a single project do not matter?
If you can use the Expand All command in one and it affects both, you neednât do it again;
It does not affect both of the instances. The two instances of each of the five projects appear to run independently of each other.
I suppose to be most thorough, you could take individual snapshots from the open Quick Reference windows before closing themâuse the Documents ⸠Snapshots ⸠menu from within the QR window; the document icon in the title bar there wonât change to show the folded corner indicating it has a snapshot, but the snapshot will be created and viewable from the main window. Then yes, go ahead and close the QR windows; it shouldnât make a difference, really, but you might as well tidy up to avoid any extra confusion with multiple windows.
OK, I understand.
I wasnât clear from that description whether you had taken two snapshots, one from each instance of the project window, and found two corresponding RTF files in the .scriv\Snapshots directory (and two content.rtf files within the \Data directory)
Sorry. Yes, it is like that. I did it again from one instance with unique chars:
https://i.imgur.com/a01R2xG.png
And from the other instance (of the same project) with other unique chars:
https://i.imgur.com/MCMzvtU.png
So the snapshots of each of the two instances are available in both of their back ups.
Thank you very much, Clive, for the very true and kind, encouraging and calming words. They give me strength (in the dark times of losing text). And many thanks for the further ideas.
This would be to do a Save As for each double-windowed project, before they are finally to be closed â one differently named for each window. Now you should have the entire working memory of each instance in its own separate and workable project.
Well, this indeed sounds like a very good idea. I didnât think of it at all.
Then my thinking would be to do a full compile of each of these full project versions, as plain text named appropriately. Now itâs easy to use the comparison tool to note how they differ.
And this one as well, very good, I would think.
the first would be to make easier use of those named snapshots. Youâd do a further Save As for each of the Save As versions just above â and then revert the appropriate named snapshots into each one. This would give you a chance to have their versions of the file, even if fully saving had disturbed this, which we canât know. Youâd do the same Compile to plain text, and make comparison, to see if more useful text or at least valued ideas could be recovered. It might be worth making this effort?
Sounds good. Sorry, what does that mean: âand then revert the appropriate named snapshots into each one.â?
finally, there are the backups themselves. It would be very tedious to do other than to use the Compile to text and compare method, as above, to see if thereâs anything in those by now which adds to recovered information. This could be the method which makes checking the backups at alll worthwhile, or some of them?
Yes, I will do that, good idea, but unfortunately I do not have that many back ups.
though each Carl-S backup in the past will have eliminated an earliest backup remaining prior to it.
That is no problem here as I did not make so many back ups that this would affect negatively. And I have copied the back ups to another folder. And I set that back up remove option of Scrivener as high as possible.
Ok, thatâs surely enough. Iâve tried to deal with or avoid variations one could think of that only make matters more possibly complicated, and stick to most straightforward methods.
You can see what you think, and if Iâve missed something, which in this scenario is certainly easy to do! Now it is most certainly time ot sleep 
Very good thoughts, many thanks. And many thanks for staying up so long to help. Good night, Clive