Apologies if this has been raised before but I just encountered it.
When working in a large file (who knows, it might happen in a small file too) I did a search and replace in one of my character files I’d copied from the character template.
Strange behavior:
The search failed to turn up Upper case instances, even though “ignore case” was selected.
The search and replace turned up fewer instances than it should have.
The text began to disappear from the file. When I clicked into another file and back into the file in question, all the text was gone. When I rebooted Scrivener, the text had returned.
And post the required information so that I can reproduce this (step-by-step instructions to reproduce)? That will make tracking and fixing something like this a lot easier. Also, if you open console.app whilst doing this, do you see any console errors?
Open a file in a big document (in my case, a character file based on the character template you provided),
do a search and replace of a phrase
watch the text in the file gradually disappear, first a few lines, and then, as you scroll around, more and more text.
Click out of the file, click back into the file, and all text is gone.
Reboot, and it’s back again.
But I have to say, I’ve tried reproducing it and I haven’t been able to. Which is useless to you, I know. If it happens again, I’ll let you know right away.
Open Project - the 2nd “bad” has returned to its previous “good” state
I’ve fiddled with it - seems to depend where the cursor is when Replace All is clicked. Sometimes everything is acutally there after close & re-open - but I even had one case, where “good” was on the screen, but could not be found - “internally” the two words were “bad” …
TCole - that sounds like an exception is getting thrown. Once an exception gets thrown, things will start acting odd - such as the drawing of text may not occur properly. Next time this happens, check out Console.app - I bet an error gets written out. That will help me find it. Unfortunately it is one for which I will have to wait to happen again.
Following up on this. To be sure that it’s not some individual thing on my iBook I tried the exact same thing on my iMac Core Duo with 10.4.10 and the latest beta - and had the same behaviour.