Details
-
Bug
-
Resolution: Incomplete
-
P2: Important
-
None
-
6.4.0
Description
When using a custom item defined in c++ that has setAcceptHoverEvents and setCursor statements to change the mouse when hovered over, the actual area that will change the mouse cursor takes any x or y difference from the window's top left twice.
Ex: If the item has a total x and y of 100 from the window's top left, the area that will trigger the mouse cursor to change when hovered will only start at a x and y of 200 from the window's top left.
It does not matter if the x and y declarations are in the parent or directly in the item, they give the same result.
Attached is a sample project showing the issue, note that when mousing over only the bottom right quadrant of the blue rectangle will trigger a mouse cursor change when hovered.