This is a bug and will be fixed shortly. In the mean time you can work around it by running:
Code: Select all
set the allowInterrupts to true
In the Message Box.
Tip: you can generally interrupt Revolution by sending it a signal (on Unix or Mac OS X), and this will allow you to interrupt even tight loops that don't accept an interruption from the keyboard (this can be useful with allowInterrupts both true and false).
Find out what process Revolution is by running top or by using ps with appropriate flags. Then run in a shell (eg the Terminal on Mac OS X),
kill -SIGHUP <pid>
Where <pid> is the ID of the Revolution process.