Menu

#381 input blocked

open
Qbix
None
5
2012-09-07
2012-07-31
mhanor
No

The emulated standard input is blocked when I do the following:
1) Start DosBox
2) Select the main DosBox window, hit Alt+Break to break into the DosBox Debugger
3) Select the main DosBox window while the emulator is halted and type a key
4) Select the DosBox Debugger window and hit F5 to resume the execution
5) Select the main DosBox window, try to type anything. At least I can't, unless I break into the Debugger, type a key while the Debugger window is selected, then resume the execution.

I've used self-build 32 bit DosBox from 0.74 sources and from trunk 3789 sources. Build using VS2010.

As a side note, shouldn't the Debugger window drop all input entered while the emulation is running? Select the Debugger window while the emulation is running, type anything you want, select the main window and hit Alt+Break. The Debugger window registers the previously typed keys.

Discussion

  • mhanor

    mhanor - 2012-07-31
     
  • Qbix

    Qbix - 2012-07-31

    could you try and press alt when the keys are blocked ?
    maybe the alt-key (or the tab key) is registered as still being pressed. (or the pause key and the game is actually in a pause loop)

    With regards to the side note, well it could, but it's not really important. I do actually abuse this feature every now and then. (starting to type when debugger is not active (debug point didn't activate yet)). but it can be fixed.

     
  • mhanor

    mhanor - 2012-07-31

    Indeed, the workaround is to press Alt in the main window, after resuming emulation.
    I've encountered the issue when switching back and forth between the two windows. By mistake, I sometimes type in the main window what I want to type in the Debugger window. Another annoyance is that Alt-Break doesn't break into the debugger if the Debugger window is selected.

     
  • mhanor

    mhanor - 2012-07-31

    Btw, the last key pressed in the emulated env, is Alt-Break. There's nothing else, and the emulated env is idling at the command prompt.

     

Log in to post a comment.