[Bug 56348] New: Bricks: Regression in SetCursorPos handling

[WineHQ Bugzilla]

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

Bug ID: 56348
           Summary: Bricks: Regression in SetCursorPos handling
           Product: Wine
           Version: 9.0
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Hi,
I wrote the puzzle game bricks, website @ http://bricks-game.de/ with a direct
download link @ http://bricks-game.de/winbricks/bricks1/bricks1.zip

While running wine version 8 on Ubunutu 22.04 I had no problems at all running
bricks!

Unfortunately after upgrading to wine 9 the program is barely usable.

After clicking on a brick and trying to move it in a valid direction, the
program rapidly moves the brick back and forth hundreds of times a second.

I can tell you that in the source code, the program is calling the SetCursorPos
Windows API function, and so the regression appears to be there.

I also tried wine staging version 9.2 and the bug is there as well.

[Bug 56348] Bricks: moving a brick causes it to rapidly alternate positions

[WineHQ Bugzilla]

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

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Bricks: Regression in       |Bricks: moving a brick
                   |SetCursorPos handling       |causes it to rapidly
                   |                            |alternate positions
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |download, regression
                URL|                            |http://bricks-game.de/winbr
                   |                            |icks/bricks1/bricks1.zip
     Ever confirmed|0                           |1
    Regression SHA1|                            |5ebb1ed132d5261f410d7ff4f99
                   |                            |c803f50752ed9
                 CC|                            |[e-mail]

--- Comment #1 from Zeb Figura  ---
Confirming. A bisect yields:

5ebb1ed132d5261f410d7ff4f99c803f50752ed9 is the first bad commit
commit 5ebb1ed132d5261f410d7ff4f99c803f50752ed9
Author: Rémi Bernon 
Date:   Fri Jun 2 12:11:21 2023 +0200

server: Queue a hardware WM_WINE_CLIPCURSOR message to the foreground
thread.

When applying a new cursor clipping rect, or to the previous foreground
    thread when foreground changes, to notify it of the cursor clipping rect
    being reset.

[Bug 56348] Bricks: moving a brick causes it to rapidly alternate positions

[WineHQ Bugzilla]

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

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Fabian Maurer  ---
Still present in wine-10.0-rc1

[Bug 56348] Bricks: moving a brick causes it to rapidly alternate positions

[WineHQ Bugzilla]

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

Rémi Bernon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
      Fixed by SHA1|                            |f6a3d80eae0694cf9c199fbe3f2
                   |                            |856dc8796ea4c

--- Comment #3 from Rémi Bernon  ---
Should be fixed with f6a3d80eae0694cf9c199fbe3f2856dc8796ea4c

[Bug 56348] Bricks: moving a brick causes it to rapidly alternate positions

[WineHQ Bugzilla]

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

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Alexandre Julliard  ---
Closing bugs fixed in 10.0-rc3.