Descriptive Problem Summary:
Setting new screen coordinates of an atom on a client's screen does not send atom/MouseExited() if the item exits the bounds of the client's cursor with that change in coordinates.
I'm unsure if this is intentional functionality but I figured this is the best place to stuff this thread.
Jun 20 2018, 6:04 pm
Not a bug