May 2013 - Wine-devel - list.winehq.org

Wacom Graphire3 tablet not detected as tablet (MacOSX 10.8)
by Andrey Upadyshev 14 May '13

14 May '13

Hi, I have Wacom Graphire3 tablet and it's working well under Windows, MacOS or MacOS + X (Inkscape). But Wine can't detect it as tablet and disables the wintab support. The actual stylus device is Device 6 [id 8|name pen|type |num_classes 2|use 4], but log says it is not apparently a tablet cursor type device. There is a wintab log: > trace:wintab32:DllMain 0x43d60000, 1, 0x0 > trace:wintab32:DllMain Initialization > trace:wintab32:TABLET_WindowProc Incoming Message 0x81 (0x00000000, > 0x0032f6b0) > trace:wintab32:TABLET_WindowProc Incoming Message 0x83 (0x00000000, > 0x0032f400) > trace:wintab32:TABLET_WindowProc Incoming Message 0x1 (0x00000000, > 0x0032f6b0) > trace:wintab32:TABLET_WindowProc Incoming Message 0x5 (0x00000000, > 0x00000000) > trace:wintab32:TABLET_WindowProc Incoming Message 0x3 (0x00000000, > 0x00000000) > trace:wintab32:LoadTablet Initializing the tablet to hwnd 0x10126 > trace:wintab32:X11DRV_LoadTabletInfo XListInputDevices reports 9 devices > trace:wintab32:X11DRV_LoadTabletInfo Device 0: [id 2|name Virtual core > pointer|type |num_classes 2|use 0] > trace:wintab32:X11DRV_LoadTabletInfo Device 1: [id 3|name Virtual core > keyboard|type |num_classes 1|use 1] > trace:wintab32:X11DRV_LoadTabletInfo Device 2: [id 4|name Virtual core > XTEST pointer|type |num_classes 2|use 4] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > warn:wintab32:X11DRV_LoadTabletInfo Skipping device 2 [name Virtual core > XTEST pointer|type ]; not apparently a tablet cursor type device. If this > is wrong, please report it to wine-devel(a)winehq.org > trace:wintab32:X11DRV_LoadTabletInfo Device 3: [id 5|name Virtual core > XTEST keyboard|type |num_classes 1|use 3] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > trace:wintab32:X11DRV_LoadTabletInfo No buttons, Non Tablet Device > trace:wintab32:X11DRV_LoadTabletInfo Device 4: [id 6|name xquartz virtual > pointer|type |num_classes 2|use 4] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > warn:wintab32:X11DRV_LoadTabletInfo Skipping device 4 [name xquartz > virtual pointer|type ]; not apparently a tablet cursor type device. If > this is wrong, please report it to wine-devel(a)winehq.org > trace:wintab32:X11DRV_LoadTabletInfo Device 5: [id 7|name xquartz virtual > keyboard|type |num_classes 1|use 3] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > trace:wintab32:X11DRV_LoadTabletInfo No buttons, Non Tablet Device > trace:wintab32:X11DRV_LoadTabletInfo Device 6: [id 8|name pen|type > |num_classes 2|use 4] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > warn:wintab32:X11DRV_LoadTabletInfo Skipping device 6 [name pen|type ]; > not apparently a tablet cursor type device. If this is wrong, please > report it to wine-devel(a)winehq.org > trace:wintab32:X11DRV_LoadTabletInfo Device 7: [id 9|name cursor|type > |num_classes 2|use 4] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > trace:wintab32:X11DRV_LoadTabletInfo ButtonInput 0: [class 1|length > 12|num_buttons 3] > trace:wintab32:X11DRV_LoadTabletInfo ValidatorInput 1: [class 2|length > 80|num_axes 5|mode 1|motion_buffer 256] > trace:wintab32:trace_axes Axis 0: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 1: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 2: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 3: [resolution 1|min_value > -65536|max_value 65536] > trace:wintab32:trace_axes Axis 4: [resolution 1|min_value > -65536|max_value 65536] > trace:wintab32:X11DRV_LoadTabletInfo Device 8: [id 10|name eraser|type > |num_classes 2|use 4] > trace:wintab32:X11DRV_LoadTabletInfo Is XExtension: Device, Keyboard, or > Pointer > trace:wintab32:X11DRV_LoadTabletInfo ButtonInput 0: [class 1|length > 12|num_buttons 3] > trace:wintab32:X11DRV_LoadTabletInfo ValidatorInput 1: [class 2|length > 80|num_axes 5|mode 1|motion_buffer 256] > trace:wintab32:trace_axes Axis 0: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 1: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 2: [resolution 1|min_value > 0|max_value 65536] > trace:wintab32:trace_axes Axis 3: [resolution 1|min_value > -65536|max_value 65536] > trace:wintab32:trace_axes Axis 4: [resolution 1|min_value > -65536|max_value 65536] > warn:wintab32:X11DRV_LoadTabletInfo Did not find a valid stylus, unable to > determine system context parameters. Wintab is disabled. > It would be great if someone can fix this problem. Thank you, Andrey Upadyshev

1 0

Re: [PATCH 3/3] d3dx9_36: Add support for D3DFMT_P8 and conversion to other ARGB formats + tests.
by Alexandre Julliard 14 May '13

14 May '13

Christian Costa <titan.costa(a)gmail.com> writes: > @@ -36,6 +36,16 @@ static void la_to_rgba(const struct vec4 *la, struct vec4 *rgba) > rgba->w = la->w; > } > > +static void index_to_rgba(const struct vec4 *index, struct vec4 *rgba, const PALETTEENTRY *palette) > +{ > + ULONG idx = (ULONG)(index->x * 255.0f + 0.5f); > + > + rgba->x = palette[idx].peBlue / 255.0f; > + rgba->y = palette[idx].peGreen / 255.0f; > + rgba->z = palette[idx].peRed / 255.0f; > + rgba->w = palette[idx].peFlags / 255.0f; > +} PALETTEENTRY doesn't seem to be the right type for what you need. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH] user32/tests: Added capture test for child window when parent window is disabled.(try 4)
by Alexandre Julliard 14 May '13

14 May '13

Guo Jian <orzhvs(a)gmail.com> writes: > This is my first patch, could you please have a review? Thank you. Looks OK, but you could probably merge it into one of the existing capture tests, it doesn't really need a brand-new window. Also when sending patches that depend on each other, please number them so that the testbot can make sense of it. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/3] ws2_32: Implement SIO_ADDRESS_LIST_CHANGE with NotifyAddrChange (resend).
by Alexandre Julliard 14 May '13

14 May '13

"Erich E. Hoover" <erich.e.hoover(a)gmail.com> writes: > The attached patch is the next step in the series of fixes for > Silverlight/PlayReady under Wine. This particular patch does not > impact Netflix, but it does impact a number of other PlayReady > streaming services (and a variety of non-streaming sites as well). > > With this patch the SIO_ADDRESS_LIST_CHANGE call gets passed on to > NotifyAddrChange, which effectively fixes a problem where Silverlight > apps can loop forever calling SIO_ADDRESS_LIST_CHANGE (Bug #32328). > Part 2 actually implements the NotifyAddrChange call on Linux, though > this patch is sufficient to resolve the bug since the overlapped IO > event no longer gets triggered. The notification is supposed to be tied to the socket. I don't think that NotifyAddrChange can do the job. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: winemac: Disable the zoom button for windows that are disabled.
by Ken Thomases 14 May '13

14 May '13

Hi Kevin, As mentioned in the other thread, I'm not seeing the problem that this is meant to solve on 10.6. I will test 10.7+ tomorrow. Also, I'm pretty sure that setting the style mask after disabling the buttons can reenable them. At least in some versions of the frameworks, we've seen that -setStyleMask: basically resets the standard buttons from scratch. Indeed, in my testing, this patch reenables the close and minimize buttons on a disabled window. Regards, Ken

1 2

[PATCH 1/2] Added test to show EnableWindow cause wrong ReleaseCapture (try 3)
by Guo Jian 14 May '13

14 May '13

Hello everyone, This is my first patch to wine, which has been submitting since the last day. Please help that what is the safe way sending patches that makes sure the patch is not corrupt by my mail client? Is it the most correct way to attach a path with .txt suffix rather than past inline? Or which mail client should I use that may avoid this problem? Thunderbird wraps long lines and join lines terminating with a space, I have to manually correct that, it does slows me down. Thanks. Guo Jian A window will lose capture if it's disabled, but it's children should not. Related to bug 33542. The test is to show that mouse capture of a window is lost when disabling its parent window. It has been tested fine with newtestbot. --- dlls/user32/tests/win.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)

2 1

Re: user32: Use PostMessage to send WM_DRAWCLIPBOARD
by Alexandre Julliard 13 May '13

13 May '13

Piotr Caban <piotr(a)codeweavers.com> writes: > --- > dlls/user32/clipboard.c | 4 +-- > dlls/user32/tests/clipboard.c | 78 > +++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 80 insertions(+), 2 deletions(-) We already have tests that show that this is wrong: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok msg.c:12683: Test failed: set viewer NULL->1: 0: the msg sequence is not complete: expected 0308 - actual 0000 msg.c:12690: Test failed: clear clipbd (viewer=owner=1): 0: the msg sequence is not complete: expected 0308 - actual 0000 msg.c:12695: Test failed: clear clipbd (viewer=1, owner=2): 1: the msg sequence is not complete: expected 0308 - actual 0000 msg.c:12700: Test failed: set viewer 1->1: 0: the msg sequence is not complete: expected 0308 - actual 0000 msg.c:12751: Test failed: clear clipbd (no viewer, owner=1): 0: the msg sequence is not complete: expected 0307 - actual 0000 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 5/5] wined3d: Pass the state and private data to shader_select
by Henri Verbeet 13 May '13

13 May '13

On 12 May 2013 15:30, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > /* Disable shaders */ > - device->shader_backend->shader_select(context, WINED3D_SHADER_MODE_NONE, WINED3D_SHADER_MODE_NONE); > + device->shader_backend->shader_select(context, WINED3D_SHADER_MODE_NONE, WINED3D_SHADER_MODE_NONE, > + NULL, device->shader_priv); I think that's a bit questionable. Passing NULL state happens to work for this set of arguments, but I don't think we want that to be part of the interface.

3 3

Re: po: Fix typos in German translation
by Julian Rüger 13 May '13

13 May '13

Hi André, > -msgstr "Datagramme gesendet" > +msgstr "Datenpakete gesendet" In all my university classes, (UDP) Datagrams were translated or referred to as "Datagramme" and more or less strictly distinguished from packets. "Vollzugriff" vs. "voller Zugriff" is a matter of taste, I picked the first because back when I used Windows, that was a common term to read, but that could have just been my firewall or something. I would have preferred for it to be added to Francois' wordlist, but whatever. Best, Julian

2 1

Re: [PATCH 3/3] iphlpapi: Implement CancelIPChangeNotify (try 2).
by Marvin 13 May '13

13 May '13

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=25553 Your paranoid android. === WXPX64 (64 bit iphlpapi) === iphlpapi.c:1077: Test failed: Overlapped IO returned c0000120, expected c0000120 === WVISTAX64 (64 bit iphlpapi) === iphlpapi.c:1077: Test failed: Overlapped IO returned c0000120, expected c0000120 === W7PROX64 (64 bit iphlpapi) === iphlpapi.c:1077: Test failed: Overlapped IO returned c0000120, expected c0000120 === TEST64_W7SP1 (64 bit iphlpapi) === iphlpapi.c:1077: Test failed: Overlapped IO returned c0000120, expected c0000120

1 0