http://bugs.winehq.com/show_bug.cgi?id=616
*** shadow/616 Sat May 25 15:03:09 2002 --- shadow/616.tmp.25959 Sat May 25 15:11:02 2002 *************** *** 2,8 **** | keyboard input not working in warcraft II | +----------------------------------------------------------------------------+ | Bug #: 616 Product: Wine | ! | Status: UNCONFIRMED Version: 20020411 | | Resolution: Platform: | | Severity: normal OS/Version: All | | Priority: P1 Component: wine-directx | --- 2,8 ---- | keyboard input not working in warcraft II | +----------------------------------------------------------------------------+ | Bug #: 616 Product: Wine | ! | Status: RESOLVED Version: 20020411 | | Resolution: Platform: | | Severity: normal OS/Version: All | | Priority: P1 Component: wine-directx | *************** *** 144,146 **** --- 144,169 ---- + if (!other) change_queue_bits( queue, 0, clr_bit ); + break; + } + + + ------- Additional Comments From Speeddymon@yahoo.com 2002-05-25 15:11 ------- + sigh myself, i didn't read to the bottom before making that last post! oops... + more than likely, it is just the fact that warcraft2 needs to be able to grab + the input devices via directx, since that patch. before it didn't matter + because the way that input messages were being handled, everything got through, + but now, dxgrab is needed for warcraft to recognize the keyboard.... i think + that your best bet would be to leave dxgrab to n in the x11drv section and + create an appdefaults section at the bottom like this: + + [AppDefaults\warcraft2.exe\x11drv] + "DXGrab" = "N" + + where the warcraft2.exe in the [] is the actual name of your warcraft2 + executable. + + thanks for the bug report though, and im glad that i was able to help you. if + you ever think you have found a bug, dont hesitate to post it here, we are + always glad to be rid of them, and if it turns out to not be one, oh well, at + least we got another satisfied user! ;) + + -Dustin \ No newline at end of file