Fixed regression caused by recent debug console cleanup. The key stroke that

invoked the debug console would repeat after the console was closed. Another
example why keyboard repeat should be centralized, I guess...

svn-id: r24649
This commit is contained in:
Torbjörn Andersson 2006-11-07 20:30:39 +00:00
parent 4c7eaf5c55
commit b1434f2632
2 changed files with 4 additions and 12 deletions

View File

@ -348,6 +348,10 @@ int Sword2Engine::go() {
if (ke) {
if ((ke->modifiers == OSystem::KBD_CTRL && ke->keycode == 'd') || ke->ascii == '#' || ke->ascii == '~') {
// HACK: We have to clear the 'repeat' flag, or
// it will probably trigger a keyboard repeat
// immediately after the debug console closes.
_keyboardEvent.repeat = 0;
_debugger->attach();
} else if (ke->modifiers == 0 || ke->modifiers == OSystem::KBD_SHIFT) {
switch (ke->keycode) {
@ -499,17 +503,6 @@ uint32 Sword2Engine::setInputEventFilter(uint32 filter) {
return oldFilter;
}
/**
* Clear the input events. This is so that we won't get any keyboard repeat
* right after using the debugging console.
*/
void Sword2Engine::clearInputEvents() {
_keyboardEvent.pending = false;
_keyboardEvent.repeat = 0;
_mouseEvent.pending = false;
}
/**
* OSystem Event Handler. Full of cross platform goodness and 99% fat free!
*/

View File

@ -156,7 +156,6 @@ public:
uint32 setInputEventFilter(uint32 filter);
void clearInputEvents();
void parseInputEvents();
bool checkForMouseEvents();