When DGDK and DGDK.NET create their own windows for rendering the DX layer, that window uses a WNDPROC or Window Procedure to receive standard events such as keyboard/mouse etc. A message loop is used to process these system events. When you substitute a new Window handle for the DX layer etc, you're asking the library to send all events and such to a new window. This includes keyboard and mouse events. If your new window doesn't contain events for catching keyboard and mouse events, DGDK will not respond to these events. That's why the input functions will no longer work as normal when you capture into a new window.
Normally when you create or subclass a window, you also get the original window's WndProc address so that events that you don't handle, you pass into the captured WndProc for it to process events. This captured WndProc address must be the original Window Procedure that DGDK created when the toolkit first initialized. I've not done this under the .NET languages, and therefore I cannot explain the technical aspect on how to do it, but this is what is needed in order to fix the keyboard and mouse events so that you can still call the oDBInput class methods.
If not, then implement your own standard keyboard/mouse event handlers for your Windows form, and ignore the DGDK input methods altogether.
Paul.
