Descriptive Problem Summary:
When changing the screen_loc of a HUD object MouseEntered() and MouseExited() are not called based on its new coordinates. Even when using Click() to change the screen_loc MouseEntered() will still be called based on the old coordinates when Click() finishes.
Numbered Steps to Reproduce Problem:
Here is a test kit. Simply mouse over the little HUD object and click it.
Expected Results:
MouseExited() should be triggered if the HUD object moves out from under the cursor.
Actual Results:
MouseExited() is triggered based on the previous screen_loc when Click() finishes.
Does the problem occur:
Every time? Yes
In other games? Yes
ID:109466
Feb 12 2011, 8:00 pm
|
|||||||||||||
Resolved
| |||||||||||||
Feb 16 2011, 5:42 am
|
|
Since our mouse enter/leave events are coupled to actual mouse movement, this could be a tricky fix. The exact same issue should apply to non-HUD objects as well.
|