Force a Display/Input-Driver? (Re: [PATCH 2/5] dinput:
to stop mouse from escaping in exclusive mode.)
wine-devel at kievinfo.com
Thu Oct 5 19:11:05 CDT 2006
Detlef Riekenberg wrote:
> On Do, 2006-10-05 at 08:09 -0600, Vitaliy Margolen wrote:
>> diff --git a/dlls/dinput/dinput_main.c b/dlls/dinput/dinput_main.c
>> + if ((mod = GetModuleHandleA( "winex11.drv" )))
> When we force wine to use a specific Display/Input-Driver, the
> driver-selection by reading the Registry is unneeded and should
> be removed.
I don't understand what are you talking about? This is not "LoadModule"
this is GetModuleHandle - it will return valid handle only if we already
have loaded winex11.drv. And as you seen, every place that uses exported
functions, check if they were assigned.
> IMHO, the clean way is to use the dynamic Driver Name, build from
> the Registry
> (preferable by a common used wine specific Function in a dll).
This functions are driver specific. And I don't see any other driver
that we have. NULL driver doesn't count - it will not work for games or
anything that might use mouse.
>> + = (void*) GetProcAddress(mod, "wine_tsx11_acquire_mouse");
> The exported name is also not generic.
What do you mean? It is specific Wine export and has no analogy with
anything else, let alone native.
As I explained, what we have to deal with is totally different from
native. And we have to do it totally different from native. Also,
existing moue grab code doesn't work for anything but some really old
ddraw programs. Out of 20 games I've tested here, none were able to grab
More information about the wine-devel