DAY and NIGHT are indeed listed in the Script Settings>Auto-Complete tab under “Scene Headings.” When I try to use it, it works fine for the first Auto-complete (INT.), but then doesn’t work for the second (DAY, NIGHT, etc). I can’t make it work manually, either.
That console message is harmless (and blast Apple for messing up and leaving it in there, as I have to explain this regularly ).
Could you please describe your EXACT process in trying to get the “Day” or “Night” auto-complete to work. If there is no error, this is unlikely to be a bug…
What happens when you click opt-Escape? Does a list appear at all? What have you actually typed when you pause and wait?
Trying to write INT. DAY in a Scene Heading. When typing “I”, the pop-up menu appears, and you can choose INT. or INT./EXT. from it.
Then, type “N”, “D” or “A” (for Night, Day or Afternoon, with or without a space before them), and nothing appears. Even pressing Cmd-. or Opt-Esc after the character.
Everything works fine when typing “M” or “E” (for Morning or Evening).
The last log I can see in the console.log is from this afternoon. Where could I read a more meaningful log?
Paolo
(Hint: It seems to me that the characters not working with the auto-complete menu, are the same used to choose the type of line, like D for Dialogue, or A for Action, from the menu in the lower-right corner.)
-Make new document
-Verify that it is set to Screenplay
-Verify that insertion point is in Scene Heading paragraph
-Type “I”
–Auto complete list pops up, offering I/E, INT. and other choices
-Use arrow key to select INT.
-Type RETURN to post INT.
-Type “FOREST”
-Type TAB
–Scrivener inserts a hyphen
-Type “D”
–Scrivener does not pop up Auto complete list.
-Type option-esc
–Scrivener does not pop up Auto complete list
-Type Cmd-period
–Scrivener does not pop up Auto complete list
–Console does not return any message
By “click,” I assume you mean “type,” as there is no mouse activity involved.
Nothing happens when I type opt-esc or cmd-. after “D”
I’m seeing this behavior as well. Autocomplete actually worked briefly but now it doesn’t seem to work at all even when hitting cmd- - or opt - esc. Nothing is displayed in the console.
popcornflix - my sincerest apologies. I made the silly mistake of not double-checking this in Tiger before posting (I have to build on the Leopard beta in order to make sure it’s compatible).
I have now recreated the problem and know what is causing it, though getting around it is going to be awkward.
Basically, this happens whenever the auto-completion list only returns one word. So, with “Night”, “Day” etc, they are the only words in the list beginning with “N” or “D”. The OS X text system does not display a list when there is only one word in it. If you type “E”, the list returns both “Evening” and “Ext.” - there is more than one word, so you get the list. If you type “EV”, though, the list again will not appear because now there is only one word in the list - “Evening”.
You can recreate this behaviour in TextEdit - try typing “Serend” and then hit opt-Escape. You will get a list of completions. Then try typing “Serendipitousl” and hit opt-Escape. The word will be completed, but there will be no list from which to choose because there can only be one - “Serendipitously”.
That works fine in TextEdit because you have to call up the auto-completion list manually, and when you do the completion gets inserted into the text automatically. In the case of script elements, however, where the list gets presented automatically after a slight pause, you most certainly do not want the word to get inserted into the text automatically as deleting text and other edits suddenly gets horrible.
The easiest fix for this is if I add a blank item at the end of the list (a single space character) when the list would otherwise return only one item, so that is what I will do.
I have spent days now on the widows and orphans bug and it’s driving me crazy. What’s worse is that I never intended to have a “widows and orphans” feature in the first place. Argh!
Can you make it hidden? Or is it put there by Apple? I don’t think you will get too many complaints if it is turned off by default and disappears. Leave concerns about widow and orphan lines to specialist programs (even LaTex does a pretty poor job of it, from memory).
This is exactly what I’m thinking of doing - I may well get rid of widows & orphans for the time being and look at it again in the future. The bug is too horrible and widows and orphans should really be the remit of a word processor anyway…
Keith,
Other than the autocomplete issue I have been using Scrivener this week for my comic scripts and it is working out great. This is really a great update. Cheers to Antony for contributing the script format too. It’s different than what I was working with but his style has actually grown on me. I can’t wait for the final release.
Congratulation! Again, you did the impossible…
As of now, it seems the new beta is working great. I like the new cosmetic updates. And I’ve yet to lose some data…
Phew - at last a fairly quiet update (as in not too many screaming bugs). I have finally got around to starting to update the Help file, so hopefully the official release isn’t too far off.
Best,
Keith