Feature Request: Breakpoint key suppression
by Mark Dynna · in Torsion · 04/19/2008 (1:10 pm) · 2 replies
I'm not even sure if this is possible but I'll post the request here anyway.
It would be real nice if Torsion, after hitting a breakpoint, could "suppress" further key presses from being passed to Torque. I use the keyboard F10 and F11 to do my "step over" and "step into" statements, and when I'm done doing my debugging and go back to Torque those keystrokes have activated the GUI Editor and/or the Mission Editor. I know I can just remap those keys in Torque, but it would sure be nice if keys pressed during a Torsion debug session didn't affect the Torque simulation.
It would be real nice if Torsion, after hitting a breakpoint, could "suppress" further key presses from being passed to Torque. I use the keyboard F10 and F11 to do my "step over" and "step into" statements, and when I'm done doing my debugging and go back to Torque those keystrokes have activated the GUI Editor and/or the Mission Editor. I know I can just remap those keys in Torque, but it would sure be nice if keys pressed during a Torsion debug session didn't affect the Torque simulation.
Associate Tom Spilman
Sickhead Games