V17 beta, debugger: STRG-S is inserting character instead of saving

[Exolon]

Hi,

V17 Beta:

I started my batch with bdebugger, after some debugging I now get an [DC3] character within the editor window instead of a saved file by pressing CTRL-S to save.

Regards

Mike

 

[rconn]

Not reproducible here. What version (32-bit or 64-bit) of TCMD are you running, and what version of Windows? Do you have any plugins loaded?

Anybody else able to reproduce this?

 

[Charles Dye]

Are you perhaps using some keyboard layout other than US English?

echo %@convert[10,16,%@winapi[user32.dll,GetKeyboardLayout,0]]

 

[Exolon]

I'm using the V17 Beta x64 on a German Win7. No plugins.

The code Charles posted results in:

C:\Program Files\JPSoft\TCMD17x64]echo %@convert[10,16,%@winapi[user32.dll,GetKeyboardLayout,0]]
4070807

 

[Exolon]

Btw: On a fresh start of the debugger all seems fine. After some time debugging scripts (single stepping, run until breakpoint) the problem reappears.

 

[rconn]

Still not reproducible here. Can you generate a reproducible failcase?

 

[Exolon]

I tried the whole day ...

Try this:

ctrl.btm containing:

echo test
pause
echo test 2

now:

bdebugger ctrl.btm

and single-step until you see the press any key message. Now stop debugging within the debugger with the stop button and the click into source window and press CTRL-F for find.

I get an character in the source window instead the find dialog and the debugger acts quirky afterwards.

 

[vefatica]

Yup. That puts "ACK" in the BTM.

 

[rconn]

This would be a problem with the Scintilla dll. I still can't reproduce it here, but I'll pass it on to the developer.

Does it behave the same in v16?

 

[vefatica]

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.

 

[rconn]

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.

No - the input focus is in the scintilla control, which handles ^S and ^F internally. The TCMD batch debugger / ide code never sees those keystrokes.

 

[Exolon]

Does it behave the same in v16?

Yes, same with V16 here.

 

[Exolon]

Beta .42 seems to work now. Thanks :-)