Actually, it is a server-client application. We would like to allow the user to typing ahead during waiting for the server respond. Therefore, we need to capture the user action and take effect later. Originally, it is a command based application. Now, we are trying to build a GUI and match the original command.
-----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of J. Merrill Sent: Friday, 24 June 2005 9:53 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Keyboard events At 07:16 PM 6/23/2005, Jonathan wrote (in part) > Does anyone have an idea how to pausing keyboard event generation from >the winform components then all the keystrokes will be remained in the >buffer until I resume them? Is there any build-in function like that or do I >have to implement on my own? I don't think that there is any "keyboard event generation" FROM "winform components". So it must be that I don't understand what you're asking. Are you possibly hoping to capture keyboard events that come in when your application is busy, so they can take effect later (when it's not busy any more)? Would it be better to avoid having your app be unresponsive to keyboard input, maybe by doing your processing in another thread (so that the main thread stays responsive)? J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
