By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!echo %@convert[10,16,%@winapi[user32.dll,GetKeyboardLayout,0]]
echo test
pause
echo test 2
bdebugger ctrl.btm
Since it happens when you stop debugging while at a PAUSE statement, I thought it might be a (fixable?) matter of where the next keystroke was expected to go.
Does it behave the same in v16?