Re: dinput questions..

l?, 12.07.2003 kl. 10.42 skrev R. N.:
> I've been trying to track down some problems with a game demo I'm trying
> to get running.  
> Problems:
> 
> 1) mouse cursor always go to position (0, 0) in the screen

I've recently investigated a similar problem in WineX 3.1 which turned
out to be some resolution issues in desktop mode. You're not using
desktop mode, are you?

> 2) pressing any key on the keyboard crashes the game and loses focus nwo
> 
> The mouse cursor problem lets you move the mouse and it appears that in
> the 10ms window of time in dinput/mouse/main.c dinput_mouse_hook() call,
> you can move the mouse around, but then resets.  So, if you are quick
> enough you can move the mouse outside of the wine desktop.

You can only do that if DXGrab is off (if it's a fullscreen app, at
least).

> The keyboard losing focus, and previously crashing the game altogether
> seems to be related to either queued requests in
> SysKeyboardAImpl_GetDeviceData() or the unimplemented stubs for dinput.

There aren't any stubs near the crash point. But there's no information
to say for certain what the problem is. Just +dinput is not enough for
either of your two problems. For the first problem, to see why the
cursor goes to 0,0 instead of the center position that dinput tries to
reset it to, I might start with something like
+dinput,+cursor,+event,+input,+message. For the second problem, a good
rule of thumb is that when debugging a crash, and a real debugger is not
within reach, one should always, always, add +seh. So I'd run with at
least +dinput,+seh. Though the easiest would still be to catch the crash
in gdb if you can.




-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1