ID:2399033
 
Resolved
MouseDrag() calls didn't fire in cases where an extreme scaling transform was used, because the cursor was technically still over the same pixel of the dragged object. The logic has been changed to fire the message for any cursor move while a button is held.
BYOND Version:512.1448
Operating System:Windows 8 Pro 64-bit
Web Browser:Chrome 68.0.3440.106
Applies to:Dream Seeker
Status: Resolved (512.1449)

This issue has been resolved.
There are more mouse calls that were not fixed with matrix scale.
MouseDrag() and MouseMove()

https://mega.nz/#!86glDbaS!8W3y2CuNuvOD0Mvmb2CeXvhoHFlNMjSkj ouz0_tuunc
Note: Split off from id:2391048
Lummox JR resolved issue with message:
MouseDrag() calls didn't fire in cases where an extreme scaling transform was used, because the cursor was technically still over the same pixel of the dragged object. The logic has been changed to fire the message for any cursor move while a button is held.
In response to Lummox JR
Wait, can you make it so a button doesn't have to be held? Then my mouse position tracking library can actually use a single stretched HUD object for the background-layer catcher instead of tiling via screen_loc.

You said a while ago that it'd be better to do that, but I had refused because moving the mouse within a "stretched pixel" doesn't actually trigger mouse movement events.
I would not be surprised if the logic he changed applies to mouse_over as well.
I'll make sure the mouseover behavior is part of this fix as well.