|
|
Post by brion on May 13, 2019 16:58:36 GMT 1
Our testing with Alpha 4v7 has been going well and we are starting to roll it out. The users pointed an issue to us. In record view mode, the key sequence Ctrl-Enter is supposed to save the current record and enter a new record. This works in Windows 7 32 bit command window, but not in vDos. In vDos nothing happens. We have tried it in both vDos window and full-screen mode and get the same result (nothing happens). We are currently on the 2018.05.01 version. Is there a way to address it?
|
|
|
|
Post by Jos on May 13, 2019 17:30:28 GMT 1
Meanwhile there’s version 2019.05.01. But that won’t change anything to Ctrl+Enter. I ran Alpha 4v7 in 2018.05.01, and Ctrl+Enter just works. Attached DOS program SCODE will show scan and ASCII codes for keypresses. I bet that will neither show Ctrl+Enter being pressed at your side. Next bet: Ctrl+Enter is a hotkey combination for some program (graphic utility program?). Jos Attachments:SCODE.COM (2.97 KB)
|
|
|
|
Post by Jos on May 13, 2019 22:45:35 GMT 1
Windows (applications) can claim (hot)key combinations, so those don’t get to vDos (and your DOS program).
vDos could reclaim specific key combinations (like the Windows shoulder taps).
I dislike (vDos) to go into Windows internals. Also, what key combinations, all that could be used by some/whatever DOS program, while claimed by some/whatever Windows program?
Jos
|
|
|
|
Post by brion on May 14, 2019 23:26:30 GMT 1
We may have discovered the issue, can you take a look? First of all, the action which we are looking at is Ctrl-Enter, which is used when adding a new record in Alpha4 to save the current new record and move to the next blank new record. When the user locally presses Ctrl-Enter on his keyboard using the Enter key on the number pad, they get a different key code in scode (Control 0x0D). If they use the Control and the Enter key located next to the quote (") key, they get the correct key sequence, Control 0x0A. When we try this in Windows 7 32-bit DOS command window, we get the correct scode sequence Control 0x0A for both Enter keys. Without Control, both Enter keys return code 0x0A in vDos. imgur.com/a/2tAWRqv |
|
|
|
Post by Jos on May 14, 2019 23:51:24 GMT 1
Don’t really know what to do with this, no other reports to NumPad issues.
Ctrl-Enter of course differs from Ctrl-NumPad-Enter. For now, instruct the users to use the regular Ctrl-Enter combination.
I first have to look into eventually impacts to other DOS programs, differentiating these key combinations (even if NTVDM doesn't)….
Jos
|
|
|
|
Post by Jos on May 15, 2019 19:36:48 GMT 1
I had a closer look; for some reason NumPad-Enter needs special attention.
I didn’t comment that piece of code, probably just to trap it before the subsequent Windows-to-DOS keyboard conversion routines turn it into the standard Enter.
But I forgot to test for the Ctrl key being pressed, so it is always returned as if Ctrl isn’t down. I’ve corrected that for the next vDos version.
Jos
|
|
|
|
Post by brion on May 16, 2019 14:44:47 GMT 1
Jos,
Do you know yet when you will post the new version?
Thanks.
|
|
|
|
Post by Jos on May 16, 2019 15:16:53 GMT 1
Will be next year.
Jos
|
|
|
|
Post by samiam on Aug 5, 2019 16:10:07 GMT 1
Good morning - I am having a similar problem - with Ctrl-Ins not being recognized by vDos - is there a new version available that does recognize it?
Currently using version: 2019-05-01
|
|
|
|
Post by Jos on Aug 5, 2019 16:32:50 GMT 1
I tested Ctrl+Ins, it seems to function ok. Where and for what is it used in A4V7?
Jos
|
|
