If the program is stuck and you are using Windows, press CTRL+ALT+DEL and start the Task Manager. Select “Movie Magic Screenwriter” from the list of applications and press the End Task button. You may have to repeat this several times to close the program.
The most common trigger is having one or more long paragraphs (usually over a page in length) somewhere in the document. This mostly happens in stage plays where there can be monologues that go on for a while. Please break up those paragraphs with something like Action and see if the program runs better. You can also try and set the program to break Action and Dialogue *only* at sentences ends under Format > Element Styles > Page Breaks.
Another trigger is having blank elements in the document. Click on Tools > Run SmartCheck and click OK to have the program remove any blank elements it finds.
You can also copy and paste your entire document into a new blank document of the same type, i.e., Screenplay, Novel, Stage Play, etc. which may help the problem.
If the program closes unexpectedly for some reason, it should ask you to retrieve a Timed Backup the next time you open the program. The Timed Backup is a separately file that gets updated as you are working every few minutes, and is designated by a .TMB extension at the end of the file name (e.g., OscarWinner_01-01-2008.tmb).
To manually retrieve a Timed Backup:
- Click on File > Open.
- From the "Files of Type" list at the bottom of the window, choose Timed Backups.
- At the top of the window, select the folder designated as the Timed Backup location; by default, this is under Documents (or My Documents) > Screenwriter Documents > Timed Backups.
- Select the Timed Backup with the name of your document (e.g. [name of your file].tmb) and click Open.
- Assuming this has most (or all) of the data you were working on, click on File > Save As and save the file into the folder where you normally store your files. You might want to opt to save under a slightly different name (e.g. [name of your file]_v2.mmsw).
NOTE: The crashing problem has been reported. The update we were working on was a long time in development and was in testing stages, but it did not perform as needed. We are looking at another way to correct the bugs that the update was supposed to correct. We realize it has a long wait for an update, but instead of releasing an update that might introduce more problems than it solves, we have gone back to reworking the bug fixes.