Re: [PDCurses] Question about virtual key codes under Windows
On Sat, 29 Jan 2005, Lars Ivar Igesund wrote: (Warning: Norwegian terminology and names follows) Funny that I should get a reply from NTNU, I completed my siv.ing. degree at IDI the summer of 2003. IDI/NTNU -- the Mecca of computer technology! ;-) NVG, wasn't that the Lade equivalent of PVV? At least until everything moved to Gløshaugen? Yes, it's true, and it still exists as an independent organization at Gløshaugen. Mvh. David Kaasen.
Re: [PDCurses] Question about virtual key codes under Windows
No problem, it was just a case of me being blind. I got the grips on the problem with key codes, but the project stalled on unicode support (which is more or less hopeless to get right in the window console). The functions in the Win32 api that are possible to use are undocumented and possible only available in XP. (Warning: Norwegian terminology and names follows) Funny that I should get a reply from NTNU, I completed my siv.ing. degree at IDI the summer of 2003. NVG, wasn't that the Lade equivalent of PVV? At least until everything moved to Gløshaugen? Lars Ivar Igesund David Kaasen wrote: Hi! Sorry for late reply... You have probably already figured this out? I haven't read the source code of pdcurses, but I think these values might be the PC codes for function keys, arrow keys and similar non-ASCII keys. IIRC, when such a key is typed, BIOS will provide a two-byte escape sequence representing the key, consisting of 0 (zero) and the key value (20, 144 etc.). This convention is probably still followed for programs run inside a console in Windows. References: http://www.google.com/[EMAIL PROTECTED] http://www.clipx.net/ng/progref/ng49c9c.php Regards, David Kaasen.
[PDCurses] Question about virtual key codes under Windows
Hi! I'm trying to write a curses-like library for D (it started out as a port of PDCurses, but I wanted to use the OO-features of D, so it turned out to be a rewrite), and I'm using PDCurses as a help to understand what's needed, especially at the OS-level. In the function getInterestingEvent in win32/pdckbd.c, several decimal values are compared with the virtual key code of the event. The result is then used as a throw away criteria, etc. What I have difficulties grokking is the meaning of these values (20, 144, 145, 16, 17, 18). It is presumably control characters of some sort, but I don't really know. Thanks for any good answers. Yours, Lars Ivar Igesund
