Can someone provide some follow up on this? There is a problem with the current
code. The way I fixed it allows the end user to set the mode with xinput. That
seems preferable to having to apply a patch to wine if the mouse in use doesn't
work.
Christopher Cope wrote:
>The way I se
wrote:
>Christopher Cope writes:
>
>> @@ -286,8 +286,10 @@ static void enable_xinput2(void)
>> class->number, class->min, class->max,
>class->resolution, class->mode,
>> XGetAtomName( data->display, class->label ));
&
On 05/01/2013 07:38 AM, Christopher Cope wrote:
On 05/01/2013 07:21 AM, Christopher Cope wrote:
I am unsure how the "enum x11drv_atoms" in the file
dlls/winex11.dev/x11drv.h works. My /usr/include/Xatom.h defines
XA_LAST_PREDEFINED as 68. Presumably, therefore XATOM_Rel_X and
X
On 05/01/2013 07:21 AM, Christopher Cope wrote:
I am unsure how the "enum x11drv_atoms" in the file
dlls/winex11.dev/x11drv.h works. My /usr/include/Xatom.h defines
XA_LAST_PREDEFINED as 68. Presumably, therefore XATOM_Rel_X and
XATOM_Rel_X should be 81 and 82 respectively. Howev
I am unsure how the "enum x11drv_atoms" in the file
dlls/winex11.dev/x11drv.h works. My /usr/include/Xatom.h defines
XA_LAST_PREDEFINED as 68. Presumably, therefore XATOM_Rel_X and
XATOM_Rel_X should be 81 and 82 respectively. However, when I dump the
values I get 195 and 196. I am attempting t
I understand the premise, but I disagree. A lot of apps that I use don't have
maintainers. However, the comments are typically helpful. I believe this should
be approached differently.
"André Hentschel" wrote:
>Am 28.04.2013 18:57, schrieb Rosanne DiMesio:
>> Forced moderation of comments coul
