Before this change, on Windows, we were returning a "no cursor" from makeCursor when the cursor bitmap was fully transparent to avoid showing a black bitmap as the cursor. But it wasn't until recently that an issue was reported about the mouse cursor leaving a trail on the screen only when it was switched to a fully transparent bitpmap (see the fixed issue for details).
By always setting a cursor mask full of ones we avoid both of the aforementioned issues.
Fix aseprite/aseprite#3989
Before this change, on Windows, we were returning a "no cursor" from makeCursor when the cursor bitmap was fully transparent to avoid showing a black bitmap as the cursor. But it wasn't until recently that an issue was reported about the mouse cursor leaving a trail on the screen only when it was switched to a fully transparent bitpmap (see the fixed issue for details). By always setting a cursor mask full of ones we avoid both of the aforementioned issues.