[Bug 37619] World of Warcraft 6.3: Can't click buttons at the lower edge of the screen

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Nov 30 14:42:49 CST 2014


https://bugs.winehq.org/show_bug.cgi?id=37619

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download
                URL|                            |http://dist.blizzard.com/do
                   |                            |wnloads/wow-installers/full
                   |                            |/World-of-Warcraft-Setup-en
                   |                            |GB.exe
                 CC|                            |focht at gmx.net
            Summary|World of Warcraft: Can't    |World of Warcraft 6.3:
                   |click buttons at the lower  |Can't click buttons at the
                   |edge of the screen          |lower edge of the screen

--- Comment #2 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

I can't reproduce this, neither in fullscreen nor in windowed mode.
Mouse clicks are recognized in whole client window area (with action bars on
the bottom).

Since you didn't specify the distro/xserver/window manager/resolution and no
other of the tenths of thousands of WoW users playing through Wine reported
this kind of issue one must assume your distro/xserver/wm might be broken.

You could diagnose mouse input in client area though ...
Start the game with a few debug channels:

--- snip ---
$ WINEDEBUG=+tid,+msg,+win wine ./wow.exe -launcherlogin -noautolaunch64bit
-launch -uid wow_engb
--- snip ---

Keep the terminal in background and move the mouse in direction of each corner.
There should be a continuous output of 'WM_MOUSEMOVE' and
'WINPOS_WindowFromPoint' (mouse cursor coordinates in client area) messages as
long as the mouse moves.

Click a few times and watch the terminal. Now there should be some
'WM_LBUTTONDOWN' and 'WM_LBUTTONUP' messages.
The 'WINPOS_WindowFromPoint' after the mouse button down message should give
you the hit coordinates (x,y offset includes border/caption in windowed mode).
Figure out the "cut-off" area where WM_LBUTTONxxx messages are no longer
recognized. Profit! ... j/k. The "cut-off" y offset vs. screen height should
give a hint.

Also try out shrinking and moving the client window in windowed mode on desktop
if the "cut-off" area moves with the window height.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list