Regarding 1) it’s not the mouse position I need - as you point out that is trivial. It’s the widget position in screen space, OR the mouse position in widget space.
Regarding 2) Widgets may move, may not… right now I’m trying to work out if the coordinate mapping can be done easily.
My app UI is custom, and fairly simple. I have my own C++ concepts of widgets and my own image widgets, buttons, scrolling lists etc. UMG however is significantly more robust and exposed to blueprint, so I’m trying to learn the ropes.
In this case I have a car steering wheel and the user drags it around to interact. Would be trivial in my own system but I want to do this in UMG.