Hello. I am having trouble with formatting under the US Stageplay option. Essentially, I can’t get the formatting to “stick” on the character setting. Whenever I select it, it goes to character for a split second then immediately changes back to scene heading.
This doesn’t happen to me with the Screenplay option.
Any ideas?
Caleb
(I love the program, by the way, and can hardly imagine writing with anything else. Mostly prose, but I’m starting to experiment with the script options.)
Which version are you using? 1.03 (the latest “official” version) or the beta from the Beta Testing thread? Could you give a step-by-step breakdown of how to reproduce this (what you are doing, what you expect to happen, and what does happen)?
Thanks for the compliments on Scrivener, by the way.
I am using version 1.03. What happens under screenplay is what seems “right” to me. I select character, I type the name, which is formatted in all caps, I hit enter and it automatically switches to dialogue, I hit enter then tab to get back to character.
In Stageplay (US), I don’t seem to be able to select character. I can open the menu and pick it, but it reverts almost too fast to see back to scene heading. When I hit enter to go to dialogue, the default is set description, not dialogue. (Which makes sense, as set desc. should be default after scene heading.)
It seems to me that everything is working perfectly except that it doesn’t want to stay on the character setting.
Strange… It might be worth downloading the new beta from the Beta Testing forum. The script writing features have been massively overhauled so that you can completely customise them (including which element comes next on tab and return etc). Be sure to read the readme.rtf file that comes with the beta, though, as Stageplay (US) no longer comes built-in - you have to install it as a custom script (easy to do, and provided with the beta, but it will be even easier with the release version).
Certainly, I cannot recreate the bug in the new beta, which is not to say that it did not exist in 1.03, just that the changes in the beta have hopefully fixed this.