Hi all, I've been working with EmulVT and Twsocket to create a net based clone of a standard windows CGA screen set up in C40 mode as interfaced to by Borland. I've been able to modify and add the appropriate methods in EmulVT.pas to create windows that are subsets of the 40x25 screen and have their home position referred to as 1,1 etc.
I also now have blinking text using a timer in the mainline application to access screen.Lines[nRow] and blink characters. Pretty cool all in all. The original DOS application now instead of directly calling Borland routines, on request, sends messages out a TWSocket and the Client, (my screen and keyboard) initializes and shows a menu just like the original DOS app. I even went as far as to unprotect two of my ports on my firewall and have a friend across town run the client software while the server on my PC filled up his CRT. Too cool. Post card of Victoria BC will be on the way next week. Next I'm really just interested in returning keyboard entry as ASCII characters or the Delphi Virtual Key Codes. With that in mind I've modified the AppMessageHandler to call my own FOnKeyDown() function and for now print out a hex value of ASCII characters and 'F1' or 'F2' etc. for the function keys. Later I'll probably just return the VK_ values inside AppMessageHandler and remove all the multi-character string capabilities that exist for a VT100 terminal. Problem is, I'm missing F10. MS Windows appears to be doing something with it and waiting till a second character appears before giving up the next key. What's so special about F10? Thanks, John Dammeyer -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
