Quote: "You could always cheat. Make your cursor a sprite and use dbSpriteCollision() on click events?
I can't think of a reason why this wouldn't work."
That's how I do it too, but more specifically, I use a hidden 1x1 sprite and keep the mouse or use a custom sprite in place of the cursor.
Quote: "@Swordsman: That does work, until your program inevitably slows down a little, and the cursor's point lags, causing undesired clicks. For most purposes it's still viable, however."
Ouch... my self esteem. Could one just run a check to see if the mouse and the hidden 1x1 sprite are in the same location before allowing a mouse click event to take place? I'm going to go test some solutions.