Open Toxic-Cookie opened 3 years ago
At that point "PressPoint" can become "HoverPoint" since you can detect a button press and write the value on press. So It'd be a change not an addition :P
At that point "PressPoint" can become "HoverPoint" since you can detect a button press and write the value on press. So It'd be a change not an addition :P
That's a valid solution and could work as well.
I think this might play with how UIX updates, hover point might take every frame in some form and can be pretty inefficient. Maybe something like that but for colliders/bounding boxes? Unsure, what was your intent for this?
There's quite a few things that could use this. Example would be transforming buttons dependet on where you click. Or making a single button work like a joystick. Using one instead of 8 buttons for menu's (example custom radial menus) or a way for use to make "curves" this could enable this alot more easily given we wouldn't need to "click" into it.
Is your feature request related to a problem? Please describe.
The button component has a bool for pressed as well as a float2 for the press point. It also has a bool for hovering but no float2 for the hover point.
Relevant issues
N/A
Describe the solution you'd like
The addition of a float2 to get HoverPoint which would essentially be PressPoint but updates while you're hovering over it.
Describe alternatives you've considered
PressPoint can be used in certain situations but if you need the HoverPoint, it simply does not exist right now.
Additional context