And yes, you would wrap the Blue in a user widget, override onMouseDown / onTouchStarted and pass Unahandled which would allow the input to bubble up in the widget hierarchy and reach the full screen black widget.
If Blue is a native image class, you can probably get away without wrapping - images can specifically override onMouseDown ā this may or may not work with Touch, never tried.
User widgets cannot be children like the picture above.
I also couldnāt find a panel that made this possible.
Actually, Iāve tried override the event in Blue and return unhandle.
The parent UMG_TEST (pictured Widget) can receive the OnMouseButtonDown / OnTouchStarted event, but I found it impossible in Black.
Iām testing the widget with the base image, but my project already has features and design implementations.
User widgets cannot be children like the picture above.
I do not see how this is even remotely relevant here. Be children is different from having children - what you show is contradicting. For user widgets to have children, one would expose Named Slots. You can then plug in any other widget there.
Already tried to return to unhandle. But, the result is that the top widget receives the mouse event. Itās not a widget thatās drawn on the back of Blue