I am using the HiDPI, 64-bit version of RC8. When I type a search term in the document Search (i.e. hit Ctrl-F to bring up the dialogue box), invisible characters are displaying as I type (e.g. dots for spaces, see screenshot). I don’t think Scrivener ever did that before. Rather more annoying is that when I hit “Enter” I get a paragraph mark and a new line, instead of executing the search (as in all previous versions). So, I now have to take my hands off the keyboard and use the mouse to click “next”. I assume this behaviour is a bug, but if it’s by design, please may I suggest it’s not an improvement?
Using the non-HiDPI RC8. Same results and a few other oddities. If you hover your mouse over the “Find” text before you try to do a search, you will see that carriage returns (CR) and line feeds (LF) are now searchable.
Unfortunately, when entering the “Find” text, if you press the enter key you are searching for it as well and not going to the Next button as it used to work. You can use the key combo Alt+N to start the search, as well as the key F3 to find next.
I was also able to “break” the Find dialog - make it non-responsive, all controls completely grayed out - by some sort of key combo after using the mouse to initiate the find next. I was able to close the find dialog and restore the find functions, but I can’t duplicate what I did to break it, yet.
Pressing Return/Enter should trigger the Find, as it used to do previously. This has been fixed and will be available in the next update.
Find, Project Search and Snapshot Search have been greatly improved. Have in mind that you must run at least once File > “Save and Rebuild Search Indexes” for Line Feed searches to work.
Awesome! Thanks, Tiho. FWIW, I still can’t “break” the find like I did that once. Not sure what I did.
Most likely you moved the focus to a different window/Scrivener non-text area(via shortcut or accidentally), which disabled the Find dialog.
many thanks!