When using overwolf dragMove feature, the mouse cursor gets out of sync with the position you started the drag, especially when trying to drag a window quickly. This happends for in-game windows.
This has been a problem since Overwolf start but is recently a problem for HearthArena as we are moving away from a full transparent window.
For 2) it is possible to out-run the window, so that you are no longer dragging it (element with the mousehandler no longer under the cursor) and need to grab it again.
So either the user train themselves to not drag windows “too fast“ or they need to Tehran them in between if this happens.
I Experipments it on desktop before too.
This behaviour exists since a long time.
The user has to either have a wierd drag behavior where their mouse position doesn’t match the position of the object they are tragger, or start another drag and wait a second before actually starting to drag. All in all, it feels like it’s laggy as a result.
I have this same exact problem for all my users, when using dragMove there is a largely variable delay on when the window starts to move and the mouse is moving so the window doesn’t keep up with the cursor
It seems that when dragging an overwolf window outside a game running in windowed mode made, the drag can get stuck and no end-event is called when this happends. I think it would be better to stop the drag as soon as you move your mouse outside the game window, and possibly add contrain functionality: Add contrain functionality to dragMove on top of it.
This problem seems to be solved fixed in 0.158. Awesome!
You might still “out-run” the dragging by a tiny bit most likely because of the delay between the actual click and the dragMove being triggered. The window cursor doesn’t automatically clip to the position where you hold your mouse down. This can be seen in the HearthARena OPK when you move the dock with a very fast click.