Debug mode app specific rather than game specific?

[GoogleCodeExporter]

Reason for:
 * Easy for devs to leave game in debug mode.
 * Odd switching of debug mode depending on which script is being tested.
 * App specific debug could have some cool information like changing variables etc visible, and a script selection menu.

Reason against:
 * Change is hard.
 * Educating devs.
 * How to handle old games with debug?

Steps:
 * Silently ignore _debug variable
 * Add a debug option from the menu when you run PyWright
 * Only allow debug switching when PyWright starts
 * When checking for _debug variable, check global instead of wrightscript variable

Out of scope for first release, but maybe later:
 * Options for level of debug (stop on missing graphics, stop on lines of code that don't do anything)
 * Extra features for debug mode that don't exist

Original issue reported on code.google.com by saluk64007@gmail.com on 31 Oct 2012 at 8:01

[GoogleCodeExporter]

Original comment by saluk64007@gmail.com on 31 Oct 2012 at 11:09

• Added labels: Milestone-0.988
• Removed labels: Milestone-0.987

[GoogleCodeExporter]

Original comment by saluk64007@gmail.com on 16 Jan 2014 at 10:32

• Added labels: Component-Engine

[GoogleCodeExporter]

Set in #854, button position is in saves which is a little weird.

Original comment by saluk64007@gmail.com on 17 Jan 2014 at 7:24

• Changed state: Started

[GoogleCodeExporter]

Fixed in commit #866

Original comment by saluk64007@gmail.com on 20 Jan 2014 at 7:45

[GoogleCodeExporter]

Original comment by saluk64007@gmail.com on 20 Jan 2014 at 7:45

• Changed state: Fixed